Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception when using Proxy Classes #407

Closed
graben opened this issue Apr 3, 2017 · 4 comments
Closed

Exception when using Proxy Classes #407

graben opened this issue Apr 3, 2017 · 4 comments
Assignees

Comments

@graben
Copy link

graben commented Apr 3, 2017

Versions since 1.25 including latest 1.31 does throwing an Exception when using Proxy Classes. There is a line of code commented under "754d332" that is causing this behavior. It's not reasonable to me why this has been introduced.

@rliesenfeld
Copy link
Member

?! What do you mean "using Proxy Classes"? Which exception is thrown? An example test would help...

@graben
Copy link
Author

graben commented Apr 9, 2017

Well, I'm using Weld (CDI) which is using Proxies at runtime. Those classes are not found by ClassFile throwing intgernal NotFoundException. I'm still not sure why this method (754d332) is called. No return value, no inner state?

Looking if I can create a small (simple) example test.

@graben graben closed this as completed Apr 9, 2017
@graben graben reopened this Apr 9, 2017
@graben
Copy link
Author

graben commented Apr 9, 2017

Example test:
test.zip

@rliesenfeld rliesenfeld self-assigned this Apr 13, 2017
@rliesenfeld
Copy link
Member

Thanks. Weld generates a synthetic subclass for each test class using CdiRunner, and JMockit attempts to read it to extract method parameter names. Naturally, in the case of synthetic subclass, JMockit should instead take the superclass, which is the actual test class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants