cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aki Yoshida <>
Subject Re: Adding value to WS-RM feature
Date Fri, 25 Mar 2011 23:44:54 GMT
Hi Dennis,
Do you want to add a plain string content element in the
wsrm-mgr:reliableMessging element?
In that case, you can add the element declaration in rmElements group
      <xs:element name="addressingNamespace" type="xs:string" minOccurs="0">

then you add the setAddressingNamespace method in RMFeature
    public void setAddressingNamespace(String addressingNamespace) {
        this.addressingNamespace = addressingNamespace;

and finally you add in the mapElement method of RMFeatureBeanDefintion
the following parsing code so that it calls the above setter.
        } else if ("addressingNamespace".equals(name)) {
            bean.addPropertyValue(name, e.getTextContent());

Similarly, you can change the RMManager based configuration to take
this parameter.

Okay. But the above is if we are to be adding this switching option to
WS-RM. But I am thinking whether we should be rather adding this
switching option to the WSA configuration. The parameter itself seems
to fit better in WSA. In this case, we add the namespace parameter to
WSA configuration and let WS-RM use whatever the namespace that WSA is
configured with. How do you think?

Regards, Aki

2011/3/25 Dennis Sosnoski <>:
> 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 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

View raw message