Re: using Axiom instead of DOM in ServiceClient.

2009-03-19 Thread keith chapman
Sounds good to me. Thanks, Keith. On Thu, Mar 19, 2009 at 9:52 AM, Pradeep Fernando wrote: > hi All, > > @ Sagara > > yes, possible to use same existing copy, I think this line gives >> wrong impression . >> >> Description descComp = reader.readWSDL(wsdlLoc); > > > Yes it mislead me. Even t

Re: using Axiom instead of DOM in ServiceClient.

2009-03-18 Thread Pradeep Fernando
hi All, @ Sagara yes, possible to use same existing copy, I think this line gives > wrong impression . > > Description descComp = reader.readWSDL(wsdlLoc); Yes it mislead me. Even the user guide at the woden site gives a wrong impression on the above method. In that case we can use DOM as

Re: using Axiom instead of DOM in ServiceClient.

2009-03-18 Thread Sagara Gunathunga
Hi Pradeep, > some latency. So why we cant work using the already acquired copy of the > WSDL. correct me if i am wrong. yes, possible to use same existing copy, I think this line gives wrong impression . >> Description descComp = reader.readWSDL(wsdlLoc); you have following options (1)

Re: using Axiom instead of DOM in ServiceClient.

2009-03-18 Thread Pradeep Fernando
Hi devs, @ sagara, try{ > WSDLFactory factory = WSDLFactory.newInstance(); > WSDLReader reader = factory.newWSDLReader(); > reader.setFeature(ReaderFeatures.VALIDATION_FEATURE_ID, true); > Description descComp = reader.readWSDL(wsdlLoc); > } > yes, I got your point. This

Re: using Axiom instead of DOM in ServiceClient.

2009-03-18 Thread Andreas Veithen
On Wed, Mar 18, 2009 at 05:57, Pradeep Fernando wrote: > hi devs, > > @ Andreas, > >> What about improving WSDL20ToAxisServiceBuilder to support DOM and/or >> Axiom directly (I think Woden supports both)? > > > I don't think that would solve our problem, since in the case of WSDL > s we parse the

Re: using Axiom instead of DOM in ServiceClient.

2009-03-17 Thread Sagara Gunathunga
Hi Pradeep, in your staring mail > 3.since the current implementation uses dom element this mechanism > results in a double parsing when its a WSDL20.possible solution is > using > Axiom instead of dom so that when namespace checking it does not parse > the entire WSDL. I agree with th

Re: using Axiom instead of DOM in ServiceClient.

2009-03-17 Thread Pradeep Fernando
hi devs, @ Andreas, > What about improving WSDL20ToAxisServiceBuilder to support DOM and/or > Axiom directly (I think Woden supports both)? I don't think that would solve our problem, since in the case of WSDL s we parse the whole document at some point. So it doesn't matter weather Dom or Axio

Re: using Axiom instead of DOM in ServiceClient.

2009-03-17 Thread Sagara Gunathunga
Hi Devs, > 2. In the current code It uses a dom Element to Represent the WSDL.But > in this scenario we need to check the namespace and if it is a WSDL11 > Get the javax.wsl.Definition from the reader or else if it is WSDL20, > serialize it and write it to a output stream so we can get it as a > i

Re: using Axiom instead of DOM in ServiceClient.

2009-03-17 Thread keith chapman
I'm not sure how complete the AXIOM implementation is. The DOM is complete. I will ask this issue on the Woden list. Thanks, Keith. On Tue, Mar 17, 2009 at 4:24 AM, Andreas Veithen wrote: > What about improving WSDL20ToAxisServiceBuilder to support DOM and/or > Axiom directly (I think Woden supp

Re: using Axiom instead of DOM in ServiceClient.

2009-03-16 Thread Andreas Veithen
What about improving WSDL20ToAxisServiceBuilder to support DOM and/or Axiom directly (I think Woden supports both)? Andreas On Mon, Mar 16, 2009 at 06:19, Pradeep Fernando wrote: > Hi Devs, > > Right now Axis2 s' ServiceClient(Dynamic serviceClient) does not > support WSDL2 as it argument. I did