Hi,
A workaround for you will be to,
1. Save the WSDL file generated by axis2.
2. Edit the types section of the WSDL to suit your needs.
3. Then you will have to generate serverside code using this edited WSDL.
4. Get the generated messagereceiver and set it as your message receirver
using the se
Hello Sanka,
Thanks for your response. But I was wondering if anything could be
specified
in the WSDL file which would indicate to AXIS2 to not emit these two tags.
Or do you think MessageBuilders is something that could come to my help
here.
The only issue in my case is that I do not have a
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 <[EMAIL PROTECTED]> wrote:
>
>
> Hello Axis team,
>
>
> I have an issue
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 brow
