Hi Guys, -- sorry for the late reply
Sanjiva Weerawarana 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. > +1 I'll fix it. > >> 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. +1 The logic is already there in the stubs which we generate given a WSDL with policy attachment. We need to move that to ServiceClient. > 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?? > > >> may be we need to refactor them (as much as possible) >> > > +1 .. I think merging (1) & (2) is definitely in order. > + 1!! I'll look into it soon. Sanka > Sanjiva. > > >
