We have several web service client applications that interact between our main client and applications and backend servers. These web service applications generate their own JAXWS stub code to interact directly with web services and implementation code to provide a clean interface between the JAXWS code and any application that wants to use it. We have had minor problems over the past few weeks, but most have been resolved.
When it came time to integrate them into the client application, we ran into numerous problems, mainly focused on JDK1.5 and 1.6 incompatibilities. Now they are resolved, but we are faced with another problem for which we do not have a solution. Web service clients use AOP to set common things, such as header credentials, exception handling, and throttling:
<aop:config>
<aop:pointcut id="pointcut" expression="execution(* MyService.*(..))" />
<aop:aspect id="throttling" ref="throttlingAdvisor">
<aop:around pointcut-ref="pointcut" method="doThrottle" />
</aop:aspect>
<aop:aspect id="errorHandling" ref="errorHandlingAdvisor">
<aop:around pointcut-ref="pointcut" method="handleExceptions" />
Every aspect relates to the POJO bean, these beans include the method specified in the configuration, with the parameter type of the org.aspectj.lang.ProceedingJoinPoint method, this is used to extract the arguments of the method I'm intercepting.
- ( applicationContext-webservicename.xml). xml JAR, , , applicationContext.xml, web.xml , .
-, , , . , java.lang.NoClassDefFoundError: ProceedingJoinPoint ( tomcat 5.5 JDK1.5.0_17).
JavaDoc java.lang.NoClassDefFoundError , , , JVM , . , , , (aspectjrt-1.5.4.jar aspectjweaver-1.5.4.jar), , , , .
? ( , )? .