[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-dev
Subject:    Re: [Axis2]Q on Policy
From:       "Srinath Perera" <hemapani () gmail ! com>
Date:       2006-02-28 13:03:21
Message-ID: f8de7ee0602280503g1e9feb8dx2ee585d1fdbc6ef8 () mail ! gmail ! com
[Download RAW message or body]

On 2/27/06, Sanjiva Weerawarana <sanjiva@opensource.lk> wrote:
> On Mon, 2006-02-27 at 15:26 -0500, Srinath Perera wrote:
> > One more thing, I am get a feeling that code o create a AxisService
> > from WSDL and policy support are scattered
> >
> > 1. AxisServiceBuilder (Based on WSDL4J .. with policy)
> > 2. ClientUtils.creatAxisService(.......) (Based on WSDL4J . without policy)
>
> These two need to do exactly the function; that is- they both must
> respect the policy stuff and not just ignore it! I suggest merging these
> two into one method in AxisServiceBuilder.
>
> > 3. WSDLBasedServiceConfigurationBuilder (Based on WOM) .. which is my doing
>
> I think what you need to do is write some logic in ServiceClient
> (ConfigContext, AxisService) to engage the right stuff based on policies
> in the AxisService. If AxisServiceBuilder does all the policy stuff
> beforehand then the policy work is already done! I don't see why you
> should be doing another approach based on WOM ..
+1


> > then there is PolicyAttachmentUtil which is related
>
> Its already used by AxisServiceBuilder isn't it??
No, it is based on WOM, and used by code generation modules

my head spins, trying to figure how the policy is handled ;).
hopefully there are no more hidden suprises. I think we need sanka and
deepal to merge the heads togeter to sort this out

Srinath

--
============================
Srinath Perera:
   http://www.cs.indiana.edu/~hperera/
   http://www.bloglines.com/blog/hemapani

[prev in list] [next in list] [prev in thread] [next in thread]