We deprecated PolicyHandler to be in favor of Interceptor. PolicyProvider
will contribute Interceptors into the invocation chain. We also discussed
the possibility to wrap a native message as an SCA message so that we can
uniformly use the Interceptor SPI to deal with the binding/implementation
specific messages. Should we look into this further?
Thanks,
Raymond
--------------------------------------------------
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
Sent: Tuesday, September 02, 2008 9:57 AM
To: <[email protected]>
Subject: Re: Reinstating policy handlers
Simon Laws wrote:
I'm looking at rationalizing the way policy implementations are provided.
We have implementation, reference and service policy providers that are
able to create interceptors that are added to the wire.
Great, sounds good to me.
I'm in the process of reinstating policy handlers (they are currently
deprecated) and updating the policy providers to create them. I want
policy handlers to be binding or implementation specific. I propose we
change the likes of
Maybe I'm not understanding, but why aren't these just policy interceptors
then?
policy-security-ws to become binding-ws-axis2-policy-security
+1
To hold such extension specific policy artifacts.
The we change the policy handler model so that they are defined in the
module to which they apply rather than being generic.
+1
That way a user
writing a policy handle for, say, the ws binding knows precisely what
they are dealing with.
To help me understand this area the first thing I've done is build some
basic authentication support for binding.ws.axis2 with the policy
handlers as they are but with the updates to the policy providers. Doing
a build now before checking this first stage in.
Regards
Simon
--
Jean-Sebastien
