[
http://jira.jboss.com/jira/browse/JBESB-731?page=comments#action_12373650 ]
Tom Fennelly commented on JBESB-731:
------------------------------------
I looked into this and haven't got it working yet. Parking it for now.
The latest issue seems to be on the client side (I'm using a JAX-WS client) where
JBossWS uses JBossRemoting as it's remoting client. The JBossRemoing InvokerLocator
balks on the remote WS url. Looking at the InvokerLocator code, it looks strange...
it's paring the URL using a rather dodgy looking home grown version of the
java.util.URI class.
Verify MTOM support when running with SOAPProcessor Action
----------------------------------------------------------
Key: JBESB-731
URL:
http://jira.jboss.com/jira/browse/JBESB-731
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.2 Milestone Release 2
Reporter: Burr Sutter
Assigned To: Tom Fennelly
Priority: Blocker
Fix For: 4.2
Refactor JBossWS Unit Tests that confirm support of MTOM when using the ESB between the
consumer and the producer via the SOAPProcessor Action
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira