Scott Nichol wrote:
> I have run some tests on the code that determines the method to invoke
> for a service, and in my tests polymorphism is handled properly.
> Therefore, you and others who have reported problems may have hit a bug
> that my tests have not.
>
> From your posts, I assume you have
>
> interface com.dewildecbt.util.Command{...}
> class com.dewildecbt.util.OperationCommand implements
> com.dewildecbt.util.Command{...}
>
> Are there any other subclasses or interfaces?
> What is the signature of the method that you think should be executed?
> What is your deployment descriptor?
I am not certain, but this problem may be related to a bug report that I
filed. The problem is that when there are certain overloaded method
signatures, at some point there is a problem on the on-the-fly wsdl
generation. There will be one extra method that wasn't actually in the
original file.
--
To unsubscribe, e-mail: <mailto:soap-user-unsubscribe@;xml.apache.org>
For additional commands, e-mail: <mailto:soap-user-help@;xml.apache.org>
