MTOM over JMS when using rampart
--------------------------------
Key: AXIS2-4081
URL: https://issues.apache.org/jira/browse/AXIS2-4081
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.4
Environment: OS: Windows XP Pro 2002 Service Pack 2
Reporter: Cathal Callaghan
There is a bug in Axis2 1.4 when using MTOM over the JMS transport.
This is only relevant when using Rampart for security.
There are two issues at hand here:
1) MTOM is only supported for JMSByteMessages
2) When using rampart for security you must specify the property "useDOOM" as
true.
We have been able to do this on the client and have been successful in sending
an MTOM'ed message to the server. However the servers response does not return
as an MTOM'ed message.
An attempted but failed workaround have been to specify the following
properties in the services services.xml file but this has not solved the issue:
<parameter name="enableMTOM">true</parameter>
<parameter name="useDoom">true</parameter>
<parameter name="JMS_MESSAGE_TYPE">JMS_BYTE_MESSAGE</parameter>
Further investigation shows that the following method, which is responsible for
creating the outgoing MessageContext does not take into consideration what
parameters have been set in the services serices.xml file.
Method:
org.apache.axis2.util.MessageContextBuilder.createOutMessageContext(MessageContext
inMessageContext)
Thanks,
Cathal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
