Bug 780864 (SOA-3319)

Summary: Missing Spring framework dependencies when using CXF web services
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Filip Nguyen <fnguyen>
Component: JBossWS, Build ProcessAssignee: Julian Coleman <jcoleman>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.2.0.ER3, 5.2.0.ER4CC: akostadinov, asoldano, fnguyen, pcheung
Target Milestone: ---   
Target Release: 5.2.0 GA, 5.2.0.ER5   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3319
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-20 12:02:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
soa-3319-additions.txt none

Description Filip Nguyen 2011-08-30 11:57:13 UTC 
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/**).
Comment 1 Aleksandar Kostadinov 2011-09-01 16:15:22 UTC 
Just FYI wsconsume and perhaps wsprovide scripts are also affected by that.
Comment 2 Filip Nguyen 2011-09-02 07:40:09 UTC 
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.
Comment 3 Julian Coleman 2011-09-18 07:59:15 UTC 
Link: Added: This issue relates to SOA-3330
Comment 4 Julian Coleman 2011-09-18 08:20:32 UTC 
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.
Comment 5 Julian Coleman 2011-09-18 08:20:32 UTC 
Release Notes Docs Status: Added: Not Required
Comment 6 David Le Sage 2011-09-18 23:27:18 UTC 
Writer: Added: dlesage
Comment 7 Filip Nguyen 2011-10-03 14:50:20 UTC 
Verified. After running CXF installer, the jars popup.
Comment 8 Aleksandar Kostadinov 2011-10-04 05:25:06 UTC 
ws*.sh/bat still don't work properly. Are all necessary dependencies also added to these scripts?
Comment 9 trev 2011-10-04 12:27:55 UTC 
Fernando thinks the scripts refer to the spring 2 jars and not the spring 3 jars in the patch, can you investigate please.
Comment 10 Alessio Soldano 2011-10-04 12:53:10 UTC 
Yes, Fernando is right. Attached you find and additional patch for fixing the scripts.
Comment 11 Alessio Soldano 2011-10-04 12:53:10 UTC 
Attachment: Added: soa-3319-additions.txt
Comment 12 Permaine Cheung 2011-10-04 14:26:40 UTC 
jbossws-cxf-3.1.2-6.SP9.5.1.soa5.el6 built with the attached patch.
Comment 13 Douglas Palmer 2011-10-04 22:34:36 UTC 
Fix will be included in the ER5 build.
Comment 14 Brian Fitzpatrick 2011-10-06 12:34:31 UTC 
Link: Added: This issue is a dependency of JBIDE-9831
Comment 15 Filip Nguyen 2011-10-20 12:02:33 UTC 
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.
Comment 16 Aleksandar Kostadinov 2011-10-20 12:48:42 UTC 
Link: Added: This issue relates to SOA-3446