Hi,
I am using MTOM with JMS. i have been sucessful in getting the client to place an MTOM jms message on a queue. Axis2 requires you to use a JMS_MESSAGE_TYPE of JMS_BYTE_MESSAGE when performing MTOM. When the server receives this message it: 1) Requires me to have specified the property: transport.jms.Operation 2) Requires me to have specified the property: transport.jms.Wrapper 3) Creates a new soap envelope and places the entire contents of the JMS message in it. This does not seem correct as the JMS message was a complete soap envelope to begin with. This also means that all custom headers are now lost. Has anyone used MTOM over JMS, and if so how did you overcome this issue? Thanks, Cathal -- View this message in context: http://www.nabble.com/JMS_BYTE_MESSAGE-doesnt-support-custom-headers-tp15829600p15829600.html Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
