That's right. Unfortunately, it mixes application data and transport data in the SOAP body content. WS-Addressing would be cleaner, the custom ODE headers are possible, too (but quite a hassle to set-up with Axis2), but currently, I share your opinion that using the message itself would be the best choice when using ODE.
Daniel Bill McCusker schrieb: > Here is a possible work around, add an element to hold the callback > endpoint to the request message definition in the process WSDL then > you can assign that endpoint from the request message to the > appropriate partner link using an assign activity. > > Daniel Luebke wrote: >> Matthieu Riou schrieb: >> >>> [...] >>> So how do you typically pass a callback endpoint for a stateful >>> service? >>> Also the use case you're describing would probably be better handled >>> using >>> correlation, don't you think? >>> >>> Cheers, >>> Matthieu >>> >> >> I would assume a WS-Addressing replyTo header. The replyTo header >> transmits the endpoint reference that is stored in the partnerlink >> afterwards. Each invoke and reply by ODE is sent to this new endpoint. >> IMO correlation alone does not solve the problem. How does ODE know >> where the partner is to be called? Correlation does not deal with >> endpoint references. >> >> Daniel >> >> >
