Hi Josh,
>My first solution was to use an custom policy in/out interceptor to read the
>@Policy annotation's uri and if surround with "${}" then build a dynamic
>policy using Neethi and set it to >PolicyConstants.POLICY_OVERRIDE. A problem
>I encountered with this approach is that I need to attach three different
>policies using different placements. Merging them may be a last resort option.
I think, if you use PolicyConstants.POLICY_OVERRIDE, you don't need to attach
policies to WSDL at all.
Dynamic policy in PolicyConstants.POLICY_OVERRIDE will overwrite all policies
in WSDL, they just will be ignored.
See the code in PolicyOutInterceptor:
// 1. Check overridden policy
Policy p =
(Policy)msg.getContextualProperty(PolicyConstants.POLICY_OVERRIDE);
if (p != null) {
// Use dynamic policy
} else if (MessageUtils.isRequestor(msg)) {
// 2. Process client policy
} else {
// 3. Process service policy
}
In your interceptor you need to load policy from somewhere, parse it with
Neethi and merge if necessary. You can load policies from WSDL, from separate
file, from database or remotely.
After set PolicyConstants.POLICY_OVERRIDE property only this policy will be
used, all your WSDL policies are irrelevant.
>A temporary hack would be to alter
>org.apache.cxf.resource.ExtendedURIResolver.resolve() to resolve a uri
>surrounded with "${}" to a spring property. I'm hoping someone here can
>suggest a better solution.
This is also possible solution. The benefits of the first one (interceptor +
PolicyConstants.POLICY_OVERRIDE) are:
- solution is dynamic (you can change policy for each call without restarting
client/service)
- policy can be loaded from any source, not necessarily from WSDL.
It really depends on your use case.
Regards,
Andrei.
From: Josh Hill [mailto:[email protected]]
Sent: Montag, 20. Mai 2013 08:42
To: [email protected]
Subject: Dynamic policies using spring properties
I annotate my web services with one class level policy and two per method to
take advantage of the placement attribute (see Fig 1). I would like to set the
policy's uri as a spring property (see Fig 2).
My first solution was to use an custom policy in/out interceptor to read the
@Policy annotation's uri and if surround with "${}" then build a dynamic policy
using Neethi and set it to PolicyConstants.POLICY_OVERRIDE. A problem I
encountered with this approach is that I need to attach three different
policies using different placements. Merging them may be a last resort option.
A temporary hack would be to alter
org.apache.cxf.resource.ExtendedURIResolver.resolve() to resolve a uri
surrounded with "${}" to a spring property. I'm hoping someone here can suggest
a better solution.
Any thoughts
Fig 1.
@WebService
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL)
@Policy(uri = "classpath:/policy/service.policy", placement =
Policy.Placement.SERVICE)
public interface ProductWS {
@WebMethod
@WebResult(name = "product-wsresponse")
@Policies({
@Policy(uri = "classpath:/policy/service-input.policy", placement =
Policy.Placement.BINDING_OPERATION_INPUT),
@Policy(uri = "classpath:/policy/service-output.policy", placement
= Policy.Placement.BINDING_OPERATION_OUTPUT)
})
ProductResponseMessage products(@WebParam(name = "product-wsrequest")
ProductRequestMessage productRequestMessage);
}
Fig 2.
@WebService
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL)
@Policy(uri = "${product.service.policy}", placement = Policy.Placement.SERVICE)
public interface ProductWS {
@WebMethod
@WebResult(name = "product-wsresponse")
@Policies({
@Policy(uri = "${product.service.input.policy}", placement =
Policy.Placement.BINDING_OPERATION_INPUT),
@Policy(uri = "${product.service.output.policy}", placement =
Policy.Placement.BINDING_OPERATION_OUTPUT)
})
ProductResponseMessage products(@WebParam(name = "product-wsrequest")
ProductRequestMessage productRequestMessage);
}
Josh Hill
Senior Java Developer
sovereign finance and banking software
A Level 1, Building C, Millennium Centre, 602 Great South Road, Greenlane,
Auckland, New Zealand
D 64 9 571 6812 P 64 9 571 6800 F 64 9 571 6899
E [email protected] W www.finzsoft.com
Please note: This email contains information that is confidential and may be
privileged. If you are not the intended recipient, you must not peruse, use,
disseminate, distribute or copy this email or attachments. If you have received
this in error, please notify Finzsoft Solutions (New Zealand) Ltd immediately
by return email and delete this email. Thank you.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
