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 the WSDL representation model without a problem. So as Sagara proposed we can work it out like this. -read the WSDL and get it as the DOM model. -compare namespaces. -if WSDL11 read it using reader and get a WSDL4J.Definition, in order to feed WSDL11ToAxisServiceBuilder -if WSD20 read it using reader(given that it supports DOM), and get a WODEN.Description to feed WSDL20ToAxisserviceBuilder. Thus we have to add a new constructor in the WSDL20ToAxisServiceBuilder supporting Woden.Description. This will make sure the consistency between WSDL20ToAxisServiceBuilder & WSDL11ToAxisserviceBuilder as the latter has a constructor supporting WSDL4J.Definiton. Thanks Andreas,Sagara & Keith for your suggestions, This seems to be the perfect solution for me. WDYT devs? cheers, Pradeep Fernando.
