On 2/13/08, Simone Maletta <[EMAIL PROTECTED]> wrote: > > there is anyone that may say to me if ODE permits to use jms transport > for a BPEL server? > I know how to activate it from Axis2, but I can't write a WSDL that bind > with a jms queue.
Hi Simone, Implementing a process that uses JMS instead of HTTP is quite easy with Axis2. In fact, there is nothing additional to do as all services created are automatically exposed via JMS if the transport is configured in Axis2. For example, if the endpoint of the process is http://localhost:8080/ode/processes/JMS/server4/Server/queue1 Then the JMS should be named: JMS/server4/Server/queue1 (IIRC it gets created automatically with ActiveMQ). The JMS Message should contain the full SOAP Message (with soap:Envelope and everything). If the MEP is request-response, the response will be sent to the queue specified in the JMSReplyTo message header. Hope this helps, alex
