Bug 780874 (SOA-3330) - Missing client jars for MTOM support
Summary: Missing client jars for MTOM support
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3330
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Build Process
Version: 5.2.0.ER3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.2.0 GA,5.2.0.ER4
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-31 09:21 UTC by Martin Vecera
Modified: 2011-10-03 15:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
SOA-P with CXF installed
Last Closed: 2011-10-03 15:31:27 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 780839 0 medium CLOSED Invalid javax.xml.ws.spi.Provider in jaxws-rt-X.Y.Z.jar after CXF installer has been run. 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 780864 0 urgent CLOSED Missing Spring framework dependencies when using CXF web services 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-3330 0 None Closed Missing client jars for MTOM support 2012-04-17 07:44:07 UTC

Internal Links: 780839 780864

Description Martin Vecera 2011-08-31 09:21:40 UTC 
project_key: SOA

webservice_mtom quickstarts demonstrates MTOM. The client part needs XMLStreamBuffer from server/${config}/soap.esb/streambuffer.xml to lookup endpoint. Quickstarts have this library on classpath and therefore everything works fine, but client should not be requested to have libraries in this directory on a classpath. Problematic is this line of code:
Service service = Service.create(wsdlURL, serviceName);
That causes: java.lang.NoClassDefFoundError: com/sun/xml/stream/buffer/XMLStreamBuffer
The issue was in SOA-P 5.1 as well but was hidden by a different bug in MTOM.
Comment 1 Martin Vecera 2011-08-31 09:28:04 UTC 
There seem to be more jars missing (stax-ex-1.1.jar for instance). Please note that this happens only with CXF stack in place.
Comment 2 Martin Vecera 2011-08-31 09:33:04 UTC 
When I run our tests that uses more MTOM features (different datatypes) I even miss org.jvnet.mimepull.MIMEMessage that is not present in any of server libraries.
Comment 3 Julian Coleman 2011-09-01 13:31:35 UTC 
The CXF installer removes the following (non-WS) jars:

  client/jaxws-tools.jar
  client/jettison.jar
  client/stax-ex.jar
  client/streambuffer.jar

but they could be used by non-WS clients.
Comment 4 Julian Coleman 2011-09-02 13:03:44 UTC 
Link: Added: This issue is a dependency of JBPAPP-7124
Comment 5 Alessio Soldano 2011-09-06 12:48:11 UTC 
Link: Added: This issue depends JBPAPP-7124
Comment 6 Alessio Soldano 2011-09-06 12:48:22 UTC 
Link: Removed: This issue is a dependency of JBPAPP-7124
Comment 7 Julian Coleman 2011-09-18 07:59:14 UTC 
Link: Added: This issue is related to SOA-3290
Comment 8 Julian Coleman 2011-09-18 07:59:15 UTC 
Link: Added: This issue is related to SOA-3319
Comment 9 Julian Coleman 2011-09-18 08:20:30 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 10 Julian Coleman 2011-09-18 08:20:30 UTC 
Release Notes Docs Status: Added: Not Required
Comment 11 David Le Sage 2011-09-18 23:26:38 UTC 
Release Notes Docs Status: Removed: Not Required Added: Not Yet Documented
Writer: Added: dlesage
Comment 12 David Le Sage 2011-09-23 03:21:53 UTC 
Release Notes Docs Status: Removed: Not Yet Documented Added: Not Required
Comment 13 Martin Vecera 2011-10-03 15:31:27 UTC 
Verified in 5.2.ER4
Note You need to log in before you can comment on or make changes to this bug.