On 03/25/2011 02:49 AM, Daniel Kulp wrote:
... HOWEVER, what might also be good is to support a contextual property as well. Whereever we setup the WS-RM stuff for the endpoint/client, we would just call something like:msg.getContextualProperty("ws-rm.addressing.namespace") and use the value it returns and just use what's configued into the RMManager if null. That would allow simple per-endpoint/client configuration as properties on the jaxws:client/endpoint elements like the ws-security-policy things.
Sounds like the way to go. Though now that I think about it, with WS-RM 1.1/1.2 support coming in it would probably be better if I name this something like "ws-rm.1_0.addressing.namespace", to make it clear that it only applies to WS-RM 1.0 exchanges. WS-RM 1.1/1.2 are speced to use the official http://www.w3.org/2005/08/addressing namespace, and I can't imagine any reason we'd want to change that back to the submission namespace.
BTW, the only way I've found to handle switching addressing namespaces with the JAXB-generated model is by changing the WS-RM schema to use an xs:any for the AcksTo element content. That allows me to build the content directly with DOM, using the correct namespace. Anybody have any better way of handling this?
- Dennis
