[SWS-366] Dynamic AOP proxies for @Endpoints result in IllegalArgumentExceptions Created: 30/May/08 Updated: 21/Jul/08 Resolved: 16/Jun/08
|Project:||Spring Web Services|
|Reporter:||Mark Diskin||Assignee:||Arjen Poutsma|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
When using AspectJ advices on Endpoint classes will causes a "java.lang.IllegalArgumentException: object is not an instance of declaring class" exception.
See these forum posts for the stack and examples.
|Comment by Arjen Poutsma [ 13/Jun/08 ]|
I am working on solving this, but as a workaround, you can use CGLIB-based proxies, rather than dynamic proxies.
|Comment by Arjen Poutsma [ 16/Jun/08 ]|
I've decided not to fix this issue, because fixing it would break backwards compatibility with older releases.
So the workaround described earlier (using CGLIB proxies by specifying proxy-target-class="true" on the aop:aspectj-autoproxy or aop:config element) is the recommended fix.
I did change the exception thrown, so you now get a nice message, suggesting CGLIB, rather than the IllegalArgumentException thrown from deep in the JDK.
|Comment by Arjen Poutsma [ 21/Jul/08 ]|
Closing issues in 1.5.3