Yes, Aki, I've done that Aki, you might want to review the WS-RM schemas. They use an embedded AcksTo element of type wsa:EndpointReferenceType, which has one or more child elements (with the wsa;Address element required).
Dennis M. Sosnoski Java SOA and Web Services Consulting <http://www.sosnoski.com/consult.html> Axis2/CXF/Metro SOA and Web Services Training <http://www.sosnoski.com/training.html> Web Services Jump-Start <http://www.sosnoski.com/jumpstart.html> On 03/26/2011 12:44 PM, Aki Yoshida wrote: > Hi Dennis, > Do you want to add a plain string content element in the > wsrm-mgr:reliableMessging element? > ... Yes, Dan pointed me at that change. > 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? The issue here is in the WS-RM data structures. The schema uses an embedded AcksTo element of type wsa:EndpointReferenceType, which has one or more child elements (with the wsa;Address element required). The namespace used on the child element(s) needs to be changed to support interoperability (but since we don't want to break backward compatibility with existing CXF users, the change needs to be optional - hence the configuration switch). We use JAXB data binding for the WS-RM data structures, but I don't know of any way to get JAXB to work with two different namespaces for the same element name except by changing it to an xs:any and generating the DOM element with the correct namespace. - Dennis
