Hide Forgot
project_key: SOA It is not possible to run web service client for CXF webservice with JARs from client directory. The problem is that new Spring framework is used in 5.2.0.ER3 (version 3x). For example class that is required at runtime org.springframework.asm.ClassVisitor used to be in client/spring-core.jar but now is located on the server side (jboss-as/server/production/deploy/spring.esb/spring-asm-3.0.3.RELEASE.jar). It is possible to easily reproduce this bug when running quickstart webservice_wssecurity with correctly set up classpath (currently the quickstart uses too wide exec-classpath which uses jars both from client's folder and from deploy/**).
Just FYI wsconsume and perhaps wsprovide scripts are also affected by that.
At least following jars need to be in client directory: spring-aop-3.0.3.RELEASE.jar, spring-asm-3.0.3.RELEASE.jar, spring-beans.jar, spring-context.jar, spring-core.jar, spring-expression-3.0.3.RELEASE.jar Also it is necessary to modify CXF installer because it adds spring jars into client directory.
Link: Added: This issue relates to SOA-3330
Resolved with revision 10079 of: src/main/patches/eap/patch_wscxf_console.xml pom.xml Commit message: SOA-3290 SOA-3319 SOA-3330 Use jbossws-cxf-installer version 5.1.2-SOA.
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage
Verified. After running CXF installer, the jars popup.
ws*.sh/bat still don't work properly. Are all necessary dependencies also added to these scripts?
Fernando thinks the scripts refer to the spring 2 jars and not the spring 3 jars in the patch, can you investigate please.
Yes, Fernando is right. Attached you find and additional patch for fixing the scripts.
Attachment: Added: soa-3319-additions.txt
jbossws-cxf-3.1.2-6.SP9.5.1.soa5.el6 built with the attached patch.
Fix will be included in the ER5 build.
Link: Added: This issue is a dependency of JBIDE-9831
After installing EDS with CXF following spring jars are copied to the client directory: spring-aop.jar spring-asm.jar spring-beans.jar spring-context.jar spring-core.jar spring-expression.jar Manifest says they are jars of spring version 3.0.6.RELEASE. So I am closing the issue.
Link: Added: This issue relates to SOA-3446