Hi all, 

I came across this post that discuss an issue regarding method overloading.
I need to make up my mind about the use of method overloading.  It certainly
comes in handy if you have a dozen apis to expose for a dozen of objects.  

Playing with wsdl2Java shown me that it does not (as of Jan 30th build)
generates stub classes for derived complex types because they are not
explicitly referenced to by any messages, instead the messages refer to the
base type, Object.

- Debug info from wsdl2Java

org.apache.axis.wsdl.toJava.DefinedType
QName:         http://xxx/xsd:Object
isReferenced?  true
[...]

org.apache.axis.wsdl.toJava.DefinedType
QName:         http://xxx/xsd:Folder
isReferenced?  false
[...]

This seems to be a strong limitation.  As a consumer of a service I need the
derived classes to be generated even though they are not directly used by
the messages.

Would the fix simply be for WSDL2Java to see that Folder is a derived type
of Object and set his "isReferenced" attribute to true to get the class
generated?  Or else should I be building my wsdl otherwise for this to
happen?

In general, how is method overloading accepted/perceived? It looks like
being a good thing to me!

Regards,
Sylvain.


-----Original Message-----
From: Russell Butek [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 25, 2002 10:18 AM
To: [EMAIL PROTECTED]
Subject: Re: Bugs in AXIS Alpha 3 version


2.  overloaded methods problem.  This is a known problem.  We've fixed our
bug this week.  Unfortunately, we depend on WSDL4J which also has a bug.
They've been notified of it.  Now, instead of only getting one registerChar
method, you get one of them twice.  I would caution you on using overloaded
methods if you can avoid it.  There are a number of places where operations
are referred to only by name, not by signature (deploy.wsdd).  So even if
this particular bug is fixed, I worry that there may be deeper issues that
we'll run into.


This message may contain privileged and/or confidential information.  If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.  Thank you.

Reply via email to