[CONF] Apache CXF Documentation > How to Define Policies

[Andrei Shakirin (Confluence)]

How to Define Policies Page edited by Andrei Shakirin Changes (4) ... Client: {code:xml} <beans xmlns="http://www.springframework.org/schema/beans" xmlns:jaxws="http://cxf.apache.org/jaxws" xmlns:cxf="http://cxf.apache.org/core" xmlns:p="http://cxf.apache.org/policy" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://cxf.apache.org/core http://cxf.apache.org/schemas/core.xsd http://cxf.apache.org/policy http://cxf.apache.org/schemas/policy.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd" http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd"> <jaxws:client id="CRMServiceClient" name="{http://services.talend.org/CRMService}CRMServiceProvider" xmlns:serviceNamespace="http://services.talend.org/CRMService" serviceClass="org.talend.services.crmservice.CRMService" serviceName="serviceNamespace:CRMServiceProvider" endpointName="serviceNamespace:CRMServicePort" address="${endpoint.prefix}/CRMServiceProvider"> <jaxws:features> <p:policies> <wsp:PolicyReference URI="classpath:/saml.policy"/> </p:policies> </jaxws:features> </jaxws:client> </beans> {code} Service: {code:xml} <beans xmlns="http://www.springframework.org/schema/beans" xmlns:jaxws="http://cxf.apache.org/jaxws" xmlns:cxf="http://cxf.apache.org/core" xmlns:p="http://cxf.apache.org/policy" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://cxf.apache.org/core http://cxf.apache.org/schemas/core.xsd http://cxf.apache.org/policy http://cxf.apache.org/schemas/policy.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd" http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd"> <jaxws:endpoint id="CRMService" xmlns:serviceNamespace="http://services.talend.org/CRMService" serviceName="serviceNamespace:CRMServiceProvider" endpointName="serviceNamespace:CRMServicePort" implementor="#CRMServiceBean" address="/CRMServiceProvider"> <jaxws:features> <p:policies> <wsp:PolicyReference URI="classpath:/saml.policy"/> </p:policies> </jaxws:features> </jaxws:endpoint> </beans> {code} ... Full Content There are basically 3 main possibilities to define WS-Policy in CXF projects: WSDL Policy attachment Spring configuration Dynamically via message context property Let look into them in details. WSDL Policy attachment WS-Policies can be attached and referenced in WSDL elements. Web Services Policy 1.5 - Attachment standard describes all possible alternatives. WS-Policies can be placed inside WSDL itself or referenced as external documents. CXF will automatically recognize, read and use policies defined or referenced in WSDL. Sample of attached policy is shown below: <wsdl:definitions name="HelloWorld" targetNamespace="http://apache.org/hello_world_soap_http" … <wsdl:service name="SOAPService"> <wsdl:port binding="tns:Greeter_SOAPBinding" name="SoapPort"> <soap:address location="http://localhost:9000/SoapContext/SoapPort"/> <wsp:Policy xmlns:wsp="http://www.w3.org/ns/ws-policy"> <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata"> <wsp:Policy/> </wsam:Addressing> </wsp:Policy> </wsdl:port> </wsdl:service> </wsdl:definitions> Spring configuration It is possible to define policies directly in Spring configuration of client and service as jaxws feature. CXF will recognize and use configured WS-Policies: Client: <beans xmlns="http://www.springframework.org/schema/beans" xmlns:jaxws="http://cxf.apache.org/jaxws" xmlns:cxf="http://cxf.apache.org/core" xmlns:p="http://cxf.apache.org/policy" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://cxf.apache.org/core http://cxf.apache.org/schemas/core.xsd http://cxf.apache.org/policy http://cxf.apache.org/schemas/policy.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd" http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd"> <jaxws:client id="CRMServiceClient" name="{http://services.talend.org/CRMService}CRMServiceProvider" xmlns:serviceNamespace="http://services.talend.org/CRMService" serviceClass="org.talend.services.crmservice.CRMService" serviceName="serviceNamespace:CRMServiceProvider" endpointName="serviceNamespace:CRMServicePort" address="${endpoint.prefix}/CRMServiceProvider"> <jaxws:features> <p:policies> <wsp:PolicyReference URI="classpath:/saml.policy"/> </p:policies> </jaxws:features> </jaxws:client> </beans> Service: <beans xmlns="http://www.springframework.org/schema/beans" xmlns:jaxws="http://cxf.apache.org/jaxws" xmlns:cxf="http://cxf.apache.org/core" xmlns:p="http://cxf.apache.org/policy" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://cxf.apache.org/core http://cxf.apache.org/schemas/core.xsd http://cxf.apache.org/policy http://cxf.apache.org/schemas/policy.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd" http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd"> <jaxws:endpoint id="CRMService" xmlns:serviceNamespace="http://services.talend.org/CRMService" serviceName="serviceNamespace:CRMServiceProvider" endpointName="serviceNamespace:CRMServicePort" implementor="#CRMServiceBean" address="/CRMServiceProvider"> <jaxws:features> <p:policies> <wsp:PolicyReference URI="classpath:/saml.policy"/> </p:policies> </jaxws:features> </jaxws:endpoint> </beans> Dynamically via message property Sometimes policies cannot be configured statically, because they are obtained or calculated dynamically for concrete message (for example using Policy Server or Service Registry). For such cases CXF provide a possibility to load policy dynamically and set it into the message context property. It can be done for example in custom interceptor that fulfils the following: Get policy from external location and build it for current message. Parse WS-Policy XML using Neethi library. Store result Policy object into PolicyConstants.POLICY_OVERRIDE message content property. Important is that this custom policy interceptor is called before CXF PolicyInInterceptor or PolicyOutInterceptor. Than CXF will automatically recognize Policy stored into this property and use it with highest priority. Stop watching space | Change email notification preferences View Online | View Changes