axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe" <dee...@opensource.lk>
Subject Re: [Axis2] Keeping targetNamespace in services.xml
Date Tue, 10 Jan 2006 04:51:06 GMT
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" <davanum@gmail.com>
To: "Sanjiva Weerawarana" <sanjiva@opensource.lk>
Cc: <axis-dev@ws.apache.org>
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 <sanjiva@opensource.lk> 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/



Mime
View raw message