Does your class exist in multiple spots on your box, and are both
referenced in your cp?
"Gus Delgado"
<gus.delgado@netquo To: <[EMAIL PROTECTED]>
tient.com> cc:
Subject: RE: no signature match
12-11-01 12:52 PM
Please respond to
soap-user
no!
-----Original Message-----
From: Brian Abbott [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 12, 2001 12:33 PM
To: '[EMAIL PROTECTED]'
Subject: RE: no signature match
Do you receive similar errors on Tomcat 3.3?
-Brian
-----Original Message-----
From: Gus Delgado [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 12, 2001 10:22 AM
To: [EMAIL PROTECTED]
Subject: no signature match
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
--
NOTICE: The information contained in this electronic mail transmission is
intended by Convergys Corporation for the use of the named individual or
entity to which it is directed and may contain information that is
privileged or otherwise confidential. If you have received this electronic
mail transmission in error, please delete it from your system without
copying or forwarding it, and notify the sender of the error by reply email
or by telephone (collect), so that the sender's address records can be
corrected.
