Folks, The /wsa:From header is optional, and CXF does not generate a default value for this if not explicitly set by the application. (Though if this header is actually set in the message addressing properties, then it will of course be included in the out-going payload).
We could quiet easily change this policy though, for example to set the /wsa:From in the outgoing response payload to default to the /wsa:To received in the corresponding incoming request. Let me know if this change would address your interop requirement. Cheers, Eoghan 2010/1/6 Craig Tataryn <[email protected]> > Was wondering if anyone knew the answer to this? We need this for > interoperability testing with our vendor. > > Craig. > > > On 30-Dec-09, at 11:37 AM, rduhard wrote: > > >> Is there a way to have CXF generate the <wsa:From> MAP on the outgoing >> response message? It seems to only generate To, Action, MessageID and >> RelatesTo elements. The client requires the the From element also be >> populated, but I haven't been able to find a way to have it included. >> <wsa:To> element is NOT anonymous on the request message if that makes any >> difference. >> >> Any help is much appreciated. >> >> thanks, >> Rebecca >> >> >> -- >> View this message in context: >> http://old.nabble.com/wsa%3AFrom-MAP-on-response-message-not-present-tp26970149p26970149.html >> Sent from the cxf-user mailing list archive at Nabble.com. >> >> >
