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) 3. WSDLBasedServiceConfigurationBuilder (Based on WOM) .. which is my doing then there is PolicyAttachmentUtil which is related may be we need to refactor them (as much as possible) Srinath On 2/27/06, Srinath Perera <[EMAIL PROTECTED]> wrote: > It seems AxisServiceBuilder create a policy popuated AxisService given a WSDL. > If so I can use that for the ServiceClient level policy support. > > Srinath > > > On 2/26/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > > On Sat, 2006-02-25 at 20:06 -0600, Deepal Jayasinghe wrote: > > > Hi Srinath; > > > > > > What I said was there is a class called AxisServiceBuilder and if you > > > are given a WSDL which has policy in it then that guy will populate > > > AxisService for that given policy, the missing part is using that policy > > > some one has to engage modules. > > > > > > I think Ajith and Sanaka has done some coding in the client side to do > > > so , if we can borrow those code create an AxisService using given wsld > > > then I think we have wt we want. > > > > > > comments ...... > > > > This needs to be done in ServiceClient right? Because until then the > > config context isn't there and the config context is what has the info > > about available modules etc.. > > > > Sanjiva. > > > > > > > -- > ============================ > Srinath Perera: > http://www.cs.indiana.edu/~hperera/ > http://www.bloglines.com/blog/hemapani > -- ============================ Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani
