You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Vinicius Carvalho <ja...@gmail.com> on 2010/01/11 14:49:52 UTC
Static WSDL problems
Hello there! We have an legacy WS built with Pojo based deployment
with Axis2. I was told that in order to override a few defaults from
axis (soap address, and some nillable properties on elements) one
should get the generated WSDL and copy it to the same folder that the
services.xml resides.
Problem is: When we do that, Axis simply stop working. When I get the
exact WSDL that is generated through:
www.myserver.com/services/MyService?WSDL copy it to the folder of
services.xml, restart tomcat. Well things get messy, and very very
messy: One is that the marshalling stop working, parameters do not get
converted I get lots of \n on string parameters for instance.
As I said, I was told that just putting the WSDL at the services.xml
folder should work, but it does not seems so.
Any ideas please?
Regards
Re: Static WSDL problems
Posted by Vinicius Carvalho <ja...@gmail.com>.
We are using Axis2 bundled with our server, using AxisServlet. Where
should this classes go? Do I still need a services.xml?
Regards
On Mon, Jan 11, 2010 at 12:49 PM, Yashvant chauhan <c....@gmail.com> wrote:
> Hi Vinicius,
>
> As per my understanding you have to do folowing things,
> 1) create a WSDL first with proper schema...
> 2) generarte server side code using the Axis2 utility wsdl2Java and update
> the *Impl java file your business logic
> 3) create a war file with whole stuff and deploy it in a webserver
>
> once you completed above three steps your service should work.
>
> Regards,
> Yashvant
>
>
> On Mon, Jan 11, 2010 at 7:19 PM, Vinicius Carvalho <ja...@gmail.com>
> wrote:
>>
>> Hello there! We have an legacy WS built with Pojo based deployment
>> with Axis2. I was told that in order to override a few defaults from
>> axis (soap address, and some nillable properties on elements) one
>> should get the generated WSDL and copy it to the same folder that the
>> services.xml resides.
>>
>> Problem is: When we do that, Axis simply stop working. When I get the
>> exact WSDL that is generated through:
>> www.myserver.com/services/MyService?WSDL copy it to the folder of
>> services.xml, restart tomcat. Well things get messy, and very very
>> messy: One is that the marshalling stop working, parameters do not get
>> converted I get lots of \n on string parameters for instance.
>>
>> As I said, I was told that just putting the WSDL at the services.xml
>> folder should work, but it does not seems so.
>>
>> Any ideas please?
>>
>> Regards
>
>
>
> --
> ********************************************
> Yashvant Singh Chauhan
> Mobile- 09845277271
> Bangalore
>
> *********************************************
>
Re: Static WSDL problems
Posted by Yashvant chauhan <c....@gmail.com>.
Hi Vinicius,
As per my understanding you have to do folowing things,
1) create a WSDL first with proper schema...
2) generarte server side code using the Axis2 utility wsdl2Java and update
the *Impl java file your business logic
3) create a war file with whole stuff and deploy it in a webserver
once you completed above three steps your service should work.
Regards,
Yashvant
On Mon, Jan 11, 2010 at 7:19 PM, Vinicius Carvalho
<ja...@gmail.com>wrote:
> Hello there! We have an legacy WS built with Pojo based deployment
> with Axis2. I was told that in order to override a few defaults from
> axis (soap address, and some nillable properties on elements) one
> should get the generated WSDL and copy it to the same folder that the
> services.xml resides.
>
> Problem is: When we do that, Axis simply stop working. When I get the
> exact WSDL that is generated through:
> www.myserver.com/services/MyService?WSDL copy it to the folder of
> services.xml, restart tomcat. Well things get messy, and very very
> messy: One is that the marshalling stop working, parameters do not get
> converted I get lots of \n on string parameters for instance.
>
> As I said, I was told that just putting the WSDL at the services.xml
> folder should work, but it does not seems so.
>
> Any ideas please?
>
> Regards
>
--
********************************************
Yashvant Singh Chauhan
Mobile- 09845277271
Bangalore
*********************************************