Dan Diephouse wrote:
[snip]
Now the question in my mind is: how do we merge this seamlessly with
policy?
I agree that there is some overlap. So I was thinking of introducing a
AbstractPolicyWSFeature class which would be roughly like so:
public class AbstractPolicyWSFeature {
public void setPolicies(Collection<Object> policies) {... }
public Collection<Object> getPolicies() { .. }
Heh heh, this CXF thing is becoming more and more like a CORBA ORB. :^)
I certainly agree with this approach.
Cheers,
-Polar
public void initialize(...) {
... logic for ensuring the policy engine is enabled and applying the
policies to the server/client/bus would go here
}
}
Or in xml form:
<client>
<features>
<reliablemessaging>
<policies>
<RMAssertion>...</RMAssertion>
</policies>
</reliablemessaging>
</features>
</client>
Now that all seems a little verbose, but it probably wouldn't be that
verbose in reality for users as
a) the features would have sensible defaults so you would only need to
specify a policy if you were overriding the defaults
b) it would seem that chances are high that they might have their policy
externally attached if they're writing policy (via
ExternalAttachmentProvider or via the wsdl attachments)
Another option would be to allow inline policies at the endpoint config:
<client>
<policies>
<RMAssertion> ... </RMAssertion>
</policies>
</client>
Finally, I'm contemplating the name "Plugins" instead. I could see
this also
applying to things like JMX configuration.
Thoughts? Better ideas?
- Dan
