I upgraded to tomcat 4.0 and when I deploy my soap service I get a
SOAP-ENV:Server error  saying "no signature match" on the method I'm
calling. Here is the signature

public request(Element root)

I can see in the source that the signature is right! Has anyone run into
this problem before? is tomcat 4.0 not looking at my classpath and finding
some other jar file that contains the Element object? how can I fix this?
Thanks in advance for your help!

-Gus

Reply via email to