27 December 2012 16:41
To: java-user@axis.apache.org<mailto:java-user@axis.apache.org>
Subject: Re: Exposed methods with a number of input parameters
To fix this problem you need to use '-g' option when you compile, in other
words you need to compile with debug on.
Deepal
Hi,
A
Ah ok thanks!
From: Deepal jayasinghe [mailto:deep...@gmail.com]
Sent: 27 December 2012 16:45
To: java-user@axis.apache.org
Subject: Re: Exposed methods with a number of input parameters
I know, I was talking about your service. When you compile your java class you
need to turn on the debug info
7 December 2012 16:41
> *To:* java-user@axis.apache.org
> *Subject:* Re: Exposed methods with a number of input parameters
>
>
>
> To fix this problem you need to use '-g' option when you compile, in
> other words you need to compile with debug on.
>
> Deep
I should have said this is for an auto generated wsdl and not one I generated
with java2wsdl.
From: Deepal jayasinghe [mailto:deep...@gmail.com]
Sent: 27 December 2012 16:41
To: java-user@axis.apache.org
Subject: Re: Exposed methods with a number of input parameters
To fix this problem you need
To fix this problem you need to use '-g' option when you compile, in
other words you need to compile with debug on.
Deepal
>
> Hi,
>
>
>
> A couple of the legacy methods I have ported to Axis 2 take individual
> input parameters instead of an object and when I look at the wsdl none
> of the para
Hi,
A couple of the legacy methods I have ported to Axis 2 take individual input
parameters instead of an object and when I look at the wsdl none of the
parameter names are defined there, is there a reason for this?
For example:
If I look at the newer methods which are defined as taki
