Hi Srinath; I dont think that AxisServiceBuilder uses WOM inside it and only two places that we use WOM is 1. Codegeneration 2. Java2WSDL generation
Regarding policy , I think the best person in Sanka he is the one who did all the policy stuff :) Srinath Perera wrote: >On 2/27/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> 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 > > > > -- Thanks, Deepal ................................................................ ~Future is Open~
