Deepal, If people have multiple wsdl's with concrete/abstract wsdls and imports between them, then we will run into problems. no?
-- dims On 1/9/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: > Hi dims ; > > As Snajiva mentioned when we code gen we have the wsdl , so lets copy that > to META-INF directory , so in that case we give higher priority to that > WSDL. And I also agree that duplicating information here and there make > people confusing. So its up to service author to take the decision whether > to put the wsdl or not. At the code gen time we copy the wsdl into META-INF > dir whether user going to use that or not. > > So if the WSDL is not there we generate WSDL for him , and there are some > thing that he can control using services.xml (like targetNameSpace etc) > > > Thanks, > Deepal > ................................................................ > ~Future is Open~ > > ----- Original Message ----- > From: "Davanum Srinivas" <[EMAIL PROTECTED]> > To: "Sanjiva Weerawarana" <[EMAIL PROTECTED]> > Cc: <[email protected]> > Sent: Monday, January 09, 2006 9:34 PM > Subject: Re: [Axis2] Keeping targetNamespace in services.xml > > > Another thing, the problem is same if one uses XSD2Java or scomp to > generate the classes and then uses the "New Feature - making java > class a web service" > > -- dims > > On 1/9/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > > On Mon, 2006-01-09 at 08:03 -0500, Davanum Srinivas wrote: > > > Sanjiva, > > > > > > this is when the wsdl is missing....and the code was generated using > > > w2j/xmlbeans. > > > > Those two statements are contradictory; the WSDL was there but we're > > losing it when WSDL2Java generates a skeleton. That's the problem we > > must fix: don't lose the WSDL! > > > > The solution is quite simple: copy the original WSDL into the generated > > stuff then all the data will be there. > > > > Sanjiva. > > > > > > > > > -- > Davanum Srinivas : http://wso2.com/blogs/ > > > -- Davanum Srinivas : http://wso2.com/blogs/
