[
http://jira.jboss.com/jira/browse/JBESB-731?page=all ]
Tom Fennelly closed JBESB-731.
------------------------------
Resolution: Done
I patched JBREM-653 on v2.2.1 of JBR locally and verified that MTOM works through JBossESB
(using the JBossRemoting gateway to the SOAPProcessor. I created a quickstart for this,
but because of the bug, it's not in the main sourceline. It's here -
http://anonsvn.labs.jboss.com/labs/jbossesb/workspace/webservice_mtom_qs/
So this works from a JBossESB perspective, but doesn't work because of the
JBossRemoting v2.2.1+ bug - JBREM-653 (may also be in earlier version of JBR). So, while
we're running against this version of JBossRemoting, MTOM will not work through the
SOAPProcessor.
We always have the alternative of creating a dedicated HTTP Gateway that doesn't use
JBR.
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.1
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