Re: FW: jms<->WS-rm<->jms

[Asankha C. Perera]

Hi Hugo I'm trying to create a complete reliable path from client to server application using JMS and WS-rm. I'm using Axis2 with sandesha and activeMQ. Something like this: Client appl<==JMS==>ClientWebservice<==WS-rm==>ServerWebservice<==JMS==>Server appl I just got it to work for a oneWay fireAndForget message, but my JMS messages are just of type MapMessage with key and value strings. We only support binary and text messages in the current implementation. How do I go about making the JMS messages soap/jms without the WS-rm parts in it? Cant you remove the WS-RM headers from the envelope, and then send the payload over JMS? Anyway, Apache Synapse is something I would strongly recommend that you look at. It will allow you to convert from HTTP/S to JMS or from RM to non-RM etc simply by configuration rather than writing code. (See http://svn.apache.org/viewvc/webservices/synapse/trunk/java/src/site/resources/Synapse_Samples.html?content-type=text%2Fhtml&view=co#Sample503) Synapse will release its 1.0 version, as soon as Sandesha2 and Rampart releases their versions compatible with Axis 1.2 More information on Synapse could be found from http://ws.apache.org/synapse/ Because I use a durable queue we don't need to add the WS-rm in the JMS/soap messages. I don't completely understand the axis manual about the JMS transport http://ws.apache.org/axis2/1_2/jms-transport.html I think it says that the webservice are only exposed over JMS so then the WS-rm parts are included ?? or not ? I don't completely understand what you mean by 'WS-RM parts included' :-) asankha --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]