With respect to your comment: ³the invoke will be called and waits and times out²
It sounds like you¹re trying to model a long running operation as a request/response operation within WSDL. If you do this, then you¹ll most likely experience timeouts at the transport layer. A better implementation is to split this long running operation into two port types. One to make the request to start the work for the service and the other to provide an operation for the service to call you back with the response. The start operation would be a one-way operation or a request-response with a simple ACK as the response (perhaps with some values to use for correlation). This would be modeled in BPEL by an invoke followed by a receive activity. You can create a partnerLinkType to model this by having a partner role for the service you¹re invoking and a myRole for your callback point. In this way, the relationship between the two port types is made explicit. As for ODE, I have not tested this but I would think that there might be a facility whereby you could have the endpoint reference for the partnerlink¹s myRole automatically populate as the reply-to header when invoking a service. It seems reasonable that the service invocation layer would support this but you¹d have to check the docs or the source code to be sure. On 10/8/09 4:18 AM, "Michael Dondrup" <[email protected]> wrote: > Dear Filip, > we are currently working on exactly the same problem, because it would > be simple and neat solution. > However we didn't get there so far, so maybe it could be interesting > to have closer look at what it is exactly that doesn't work. > Do you have a process defined, that fails? Then maybe you could send > the process files so we could have a look it? > > We found that the WS-addressing did not seem to work with axis2 1.4.1 > and you should try axis2 1.5 on the service side. > To enable wsa support and asynchronous invocation add the following to > your services.xml within the service tags: > > <module ref="addressing" /> > <parameter name="messageReceiver.invokeOnSeparateThread">true</ > parameter> > > There will be other problems however: > - providing the correct port, role and partnerlink type, in the bpel > process for the service to reply to > - If I try to use a <invoke> and <receive> secence for invoking the > service, the invoke waits for the service to reply even though the > wsa:replyto works and the invoke will be called and waits and times > out. > The documentation on this topic is unfortunately totally incomplete. > Maybe we can try to resolve this together. > Best > Michael > > Am 07.10.2009 um 20:40 schrieb Filip Majernik: > >> > Hi, >> > I want to invoke an asynchronous Web Service from ode, but I cannot >> > figure >> > out how to change wsa:ReplyTo header. I've read about the EPR >> > configuration >> > on the ode website and tried something like this: >> > >> > <bpel:assign> >> > <bpel:copy> >> > <bpel:from> >> > <bpel:literal> >> > <wsa:EndpointReference xmlns:wsa=" >> > http://www.w3.org/2005/08/addressing";> >> > <wsa:Address> >> > http://localhost:8080/axis2/services/MyService</wsa:Address> >> > <wsa:ReplyTo><wsa:Address> >> > http://localhost:8080/axis2/services/ReplyToService >> > </wsa:Address></wsa:ReplyTo> >> > </wsa:EndpointReference> >> > </bpel:literal> >> > </bpel:from> >> > <bpel:to partnerLink="testPartnerLink"/> >> > </bpel:copy> >> > </bpel:assign> >> > >> > but it isn't working. Does anyone maybe have a working example of >> > changing >> > the wsa:ReplyTo header (and invoking and asynchronous service) when >> > invoking >> > a service??? Or is it possible at all? >> > >> > Btw. my configuration is: >> > apache ode 1.3.2 >> > the webservice I am invoking is running on apache axis 1.4 >> > >> > Thank you guys in advance. >> > Filip > > > -- Mark Ford MIT Lincoln Laboratory 244 Wood Street Lexington MA 02420 (781) 981-1843
smime.p7s
Description: S/MIME cryptographic signature
