Dan As Chathura also said, Synapse basically does what you want - out-of-the-box. We already have built and tested samples where we do:
XML/JMS->SOAP mapping and SOAP/WSRM->XML/JMS We have also done plain-text/JMS -> XML/SOAP. Synapse is simply configured using an XML config file. If you send me an example message or two I can help you create the config to test it. Paul On 5/8/07, Daniel Feist <[EMAIL PROTECTED]> wrote:
Hi, I am attempting to implement a web-services using a web service stack such as axis in order to export functionality through a web service defined by wsdl but with a twist...I want to integrate this into a message based esb type architecture. What i want to do is the following: 1) WSDL first development 2) Http transport 3) Phase/handlers as normal 4) BUT receiver does not invoke a service but rather forwards message (SOAP payload, as defined in WSDL) to a message broker ( e.g. JMS queue) where it will be routed to the service implementation. I don't want to attempt to do this with axis1, and at having quickly looking at other web service stacks it doesn't look particularly easy. I was wondering if with the new more open, message based architecture of axis2 this could be implemented, even if it means using axis2 programatically instead of via config file and where I should start looking...? thanks, Dan
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
