axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanka Samaranayake" <ssa...@gmail.com>
Subject Re: Hi - A clarification.
Date Thu, 24 Jul 2008 09:01:51 GMT
I'm afraid you can't do that if the service is deployed as a POJO Web
service. One alternative would be to handle those two elements at the client
side via a generated stub.

Sanka

On Wed, Jul 23, 2008 at 5:37 PM, Dister Kemp <dister.kemp@gmail.com> wrote:

>
>
> Hello Axis team,
>
>
> I have an issue on which I could not a find a way to resolve with Axis2.
>
> I have a server running Axis2 on Tomcat with my POJO app. which
> exposes some webservices via REST.
>
> There is a webservice - register which returns a string - but is basically
> XML.
> Now the return on the browser when hitting a webservice endpoint.
> (register)
> it comes as
>
> <ns:registerResponse xmlns:ns="http://abc.com/">
>
>
>
> <ns:return>
>    &lt;?xml version="1.0" encoding="utf-8"?>&lt;string xmlns="http://abc.com/">&lt;abc>&lt;register>111
&lt;/register>&lt;/abc>&lt;/string>
>
>
>
> </ns:return>
> </ns:registerResponse>
>
>
> As you can see there are two outer tags <ns:registerResponse> and
> <ns:return>
> which is causing my XML Parser on the client side to fail.
>
> Is there a way to disable those two tags that AXIS2 is sending, so that the
> XML tag I am sending is the top level lag and that way my client XML parser
> would work.
>
>
> Any pointers in this regard is highly appreciated.
>
> Thanks
> Dister
> _____________
>
>
>
>


-- 
Sanka Samaranayake
WSO2 Inc.

http://sankas.blogspot.com/
http://www.wso2.org/

Mime
View raw message