hi,
I faced the similar problem. But we are running ServletExec. The problem occured due to a classloader issue, where the way ServletExec loaded classes created a mismatch between the class comparisons. My service classes were residing in a tree outside the ServletExec install dir, but still in the ServletExec classpath. The soap related class files were under the ServletExec install directory. The way in which ServletExec loaded classes was that, the classes found under its install directory were loaded through ServletExecClassLoader, while those in the classpath but outside the install directory were loaded through the JDKClassLoader. Since my soap classes were in the classpath, Envelope.class for example, was found in both cases but loaded with different classloaders. I went ahead and separated/removed the SOAP classes from the soap.war, created a soap.jar and put that outside the ServletExec install directory but still in the classpath where all my other jars reside. This worked perfectly..... my 2 cents... ram "C. Schlegelmilch" <[EMAIL PROTECTED]> on 04/27/2002 04:29:55 PM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] cc: Subject: RE: No Signature Match This makes sense and was my first suspicion. But there is no doubt that my client is calling an identical method to what's deployed on the service so the problem isn't obvious. I was told it was a classloader problem but I've yet to resolve it down to that. Any more ideas? --- "W. Scott Grant" <[EMAIL PROTECTED]> wrote: > A signature match usually means that the parameters > you send to > the method do not exactly match the expected order > listed. In other > words if you have the following method > > run(String a, String b, int c) and you try to call > it using > > run(int c, String a, String b) you will get a > signature error. > > > -----Original Message----- > > From: C. Schlegelmilch > [mailto:[EMAIL PROTECTED]] > > Sent: Friday, April 12, 2002 3:17 PM > > To: [EMAIL PROTECTED] > > Subject: No Signature Match > > > > > > Hello, > > > > I've searched the archives and the web and have > yet to > > see a solid answer that works for me: > > > > With a SOAP Messaging service implemented using > Apache > > SOAP. My service calls a method called run(). It > > contains the following signature: > > > > public void run (org.apache.soap.Envelope > > env,org.apache.soap.rpc.SOAPContext > > reqCtx,org.apache.soap.rpc.SOAPContext resCtx) > > > > My service constantly returns the following error: > > Exception while handling service request: > > > com.cssde.server.RecordRouter.run(org.apache.soap.Envelope,org.apa > > > che.soap.rpc.SOAPContext,org.apache.soap.rpc.SOAPContext) > > -- no signature match > > > > Have no clue why. > > > > Running Tomcat 4.0.1 on Win2000 with JDK 1.3.1. > > > > Any ideas? > > > > Thanks, > > > > Craig Schlegelmilch > > > > __________________________________________________ > > Do You Yahoo!? > > Everything you'll ever need on one web page > > from News and Sport to Email and Music Charts > > http://uk.my.yahoo.com > > > > __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
