Andrea Smyth <[EMAIL PROTECTED]> writes: > There several ways to do this:
Thank you for your very detailed reply. > 1. Using WS-Policy: > Enable the policy framework (by setting the "enabled" attribute of the > PolicyEngine to true) and making sure that a Policy with an Addressing > assertion is attached to the WSDL service, port, portType or interface > (see cfg file addr.xml for system test > org.apache.cxf.systest.ws.policy.AddressingPolicyTest) I wound up getting this to work using an inline policy in my WSDL file. What confused me is the wsp:Optional attribute. If I indicate that the wsam:Addressing assertion is optional, the client never sends the addressing headers. Is there some way for the server to indicate the headers are optional (be it in WSDL or as an attachment), but still control whether or not the client sends the addressing headers? > 2. Using CXF Features: > This is relatively new, and I don't know much about them, but see cfg > file addr-inline-policy.xml for system test > org.apache.cxf.systest.ws.policy.AddressingInlinePolicyTest I'm looking into this one today. I see that the addressing policy is attached to an endpoint via the jaxws:features element. Two questions: o Does this style of policy specification also require definition of the bean with id org.apache.cxf.ws.policy.PolicyEngine of class org.apache.cxf.ws.policy.spring.InitializingPolicyEngine? o How can we find out what all the possible features are that can be bound in this manner? -- Steven E. Harris
