How does this work with a POJO deployment then? I haven't tried it,
but the documentation seems to indicate that with properly annotated
POJO classes, super-class methods will be included.
Is there a different Java2wsdl converter that works under the covers
with a POJO deployment?
Maybe that explains why the package path for the included java2wsdl
converter doesn't match up with the rest of the axis2 code?
If I continue building the WSDL with the converter from Axis(1) - what
are the chances that Axis2 will be happy with that WSDL? And in that
case, should I use the WSDL -> java converter from Axis1 or Axis2?
It seems a little strange to have a 3rd generation product release all
the way up to version 1.3 - and it still lacks basic functionality of
the 2nd generation product
Thanks,
Dan
On Mon, Apr 7, 2008 at 12:12 AM, Suran Jayathilaka <[EMAIL PROTECTED]> wrote:
> Hi Dan,
>
> The inclusion of super-class methods is currently unavailable in Axis2
> java2wsdl.
> This capability is in the works.
>
> Suran.
>
> Dan Armbrust wrote:
>
> >
> >
> >
> > I'm trying to migrate some code from Axis (1.2.1, I think) to Axis2 1.3.
> >
> > I can't seem to figure out how to make the java2wsdl tool in Axis2
> > properly generate method signatures for a superclass.
> >
> > The old java2wsdl tool automatically included methods from the super
> > class in the generated wsdl.
> >
> > What am I missing?
> >
> > Is there more doc somewhere on the java2wsdl tool - other than:
> > http://ws.apache.org/axis2/1_3/reference.html ?
> >
> > Thanks,
> >
> > Dan
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
