Re: Problem getting the SOAPContext

[Robert Dietrick]

Indeed, Scott is correct. I had this problem previously and never quite resolved it. I just tested it, and I'm now getting passed a valid SOAPContext object. I probably had a soap.jar in Tomcat's lib/ directory before.

-rob

Scott Nichol wrote:

You may have set up a situation where the SOAPContext class is loaded by
two different class loaders, so the SOAPContext parameter is not the
same class as the SOAPContext RPCRouter wants to match.

I you deploy Apache SOAP on Tomcat 4 and your service classes use any
Apache SOAP classes (as yours now does), your service classes must be
placed in the Apache SOAP webapp, e.g.
$CATALINA_HOME/webapps/soap/WEB-INF/classes/sage2/src/Sensors/Core2/Repo
rter.class. Tomcat should not have any other place to load Apache SOAP
from, e.g. there should not be a soap.jar in $CATALINA_HOME/lib or
$JAVA_HOME/jre/lib/ext.

Scott Nichol

----- Original Message -----
From: "Ladwig, Mike" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 11, 2002 1:25 PM
Subject: Re: Problem getting the SOAPContext

I've gotten past the original error; my service object needed soap.jar

in

it's classpath. I thought it was, but...

Now I have a different problem: I'm getting a response fault with

message

"Exception while handling service request:
sage2.src.Sensors.Core2.Reporter.Start(java.lang.String) -- no

signature

match". I've looked at the RPCRouter.java source and it appears that

I'll

get this same exception regardless of which lookup method (parameters

or

SOAPContext+parameters) failed. The second lookup shouldn't be

failing, as

far as I can tell :-(

Still stuck...

mike.

--
To unsubscribe, e-mail:

<mailto:[EMAIL PROTECTED]>

For additional commands, e-mail:

<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>