Re: Tomcat classloader problem?

[Chris Malley]

Chris Malley wrote:
[...]
> I'm experiencing a problem with SOAP message-style services
> when using Tomcat 4.01.  When trying to access any message-style
> SOAP service, my client receives a "no signature match" fault.
[...]

Remy Maucherat wrote:
[...]
> > Moving soap.jar to $CATALINA_HOME/webapps/soap/WEB-INF/lib/soap.jar should
> > solve the problem, and could be used as a workaround. Alternately, you can
> > remove from $CATALINA_HOME/webapps/soap/WEB-INF/classes/ the classes which
> > are also present in the JAR.

Glenn Nielsen wrote:
> 
> I agree with Remy, we use soap2.2 in Tomcat 4.01 just by installing
> the soap.war file.
> 
> Glenn

Glenn: Are you using message-style SOAP services, or RPC-style?
 
Using only soap.war does indeed work just fine for RPC-style,
but I get the SOAP fault shown below for message-style services;
org.apache.soap.Envelope isn't found.

Suggestions?

-Chris



http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"; 
xmlns:xsd="http://www.w3.org/1999/XMLSchema";>


SOAP-ENV:Server
Exception while handling service request:
org/apache/soap/Envelope<
/faultstring>
/soap/servlet/messagerouter

java.lang.NoClassDefFoundError: org/apache/soap/Envelope
at java.lang.Class.getMethod0(Native Method)
at java.lang.Class.getMethod(Class.java:888)
at
org.apache.soap.util.MethodUtils.getEntryPoint(MethodUtils.java:114)
at
org.apache.soap.util.MethodUtils.getMethod(MethodUtils.java:548)
at
org.apache.soap.util.MethodUtils.getMethod(MethodUtils.java:528)
[...]
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1011)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1106)
at java.lang.Thread.run(Thread.java:484)




 


-- 
Chris Malley
PixelZoom, Inc. Voice: +1.303.494.8849
835 Orman Drive EMail: [EMAIL PROTECTED]
Boulder CO 80303-2616

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Tomcat classloader problem?

[Chris Malley]

Glenn Nielsen wrote:
> 

> >
> > > Chris Malley wrote:
[...]
> > > I'm experiencing a problem with SOAP message-style services
> > > when using Tomcat 4.01.  When trying to access any message-style
> > > SOAP service, my client receives a "no signature match" fault.

[...]
> > Moving soap.jar to $CATALINA_HOME/webapps/soap/WEB-INF/lib/soap.jar should
> > solve the problem, and could be used as a workaround. Alternately, you can
> > remove from $CATALINA_HOME/webapps/soap/WEB-INF/classes/ the classes which
> > are also present in the JAR.
> >
> > Note: I don't consider this a Catalina problem, but more a questionable
> > packaging choice of the SOAP binary.
> >
> > Remy
> >
> 
> I agree with Remy, we use soap2.2 in Tomcat 4.01 just by installing
> the soap.war file.
> 
> Glenn
>

-- 
Chris Malley
PixelZoom, Inc. Voice: +1.303.494.8849
835 Orman Drive EMail: [EMAIL PROTECTED]
Boulder CO 80303-2616

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Tomcat classloader problem?

[Chris Malley]

Thanks, now I understand what's going on (though I
still don't understand how it manifests itself as a
"no signature match" for my service).

While I've always thought that the packaging of the SOAP
binary was a little strange, one could also argue
that the Catalina classloader could be a bit smarter
about things like this.

In any case, judging by the number of people who have 
contacted me since I posted, I'm not the only one 
experiencing this problem.  It should at least be 
documented in some hopefully-soon-to-be-written
"installing Apache SOAP 2.2 with Tomcat 4" doc.

How do you suggest that this be resolved?
Should I bring this to the attention of someone
in particular in the Apache SOAP group?

-Chris 


Remy Maucherat wrote:
>
> > I'm experiencing a problem with SOAP message-style services
> > when using Tomcat 4.01.  When trying to access any message-style
> > SOAP service, my client receives a "no signature match" fault.
[...]
> 
> The problem is that there are class conflicts, as half of the SOAP classes
> are in the webapp CL, and will be loaded from there (since the CL won't
> delegate), and the rest will be loaded from the shared CL. The conflicts
> will occur because the SOAP classes loaded from the shared CL will also load
> a "different" copy of the same SOAP classes from soap.jar.
> 
> Moving soap.jar to $CATALINA_HOME/webapps/soap/WEB-INF/lib/soap.jar should
> solve the problem, and could be used as a workaround. Alternately, you can
> remove from $CATALINA_HOME/webapps/soap/WEB-INF/classes/ the classes which
> are also present in the JAR.
> 
> Note: I don't consider this a Catalina problem, but more a questionable
> packaging choice of the SOAP binary.
> 
> Remy


-- 
Chris Malley
PixelZoom, Inc. Voice: +1.303.494.8849
835 Orman Drive EMail: [EMAIL PROTECTED]
Boulder CO 80303-2616

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Tomcat classloader problem?

[Remy Maucherat]

> I'm hoping someone here can help me with this. The folks
> on soap-user directed me to tomcat-user, and the tomcat-user
> folks suggested I try tomcat-dev.  So here I am...
>
> I'm experiencing a problem with SOAP message-style services
> when using Tomcat 4.01.  When trying to access any message-style
> SOAP service, my client receives a "no signature match" fault.
> I have no problem with RPC-style SOAP services, the same
> message-style SOAP services work fine with Tomcat 3.2.3,
> and the signature of the my message-style services is of
> the correct form; ie:
>
>   public void serviceName( Envelope env, SOAPContext req, SOAPContext
> res )
> throws IOException, MessagingException;
>
> What makes me think that this may be a Tomcat classloader
> problem is that I can make the fault go away by removing
> $CATALINA_HOME/webapps/soap/WEB-INF/classes/org/.
> But I don't understand why this makes the fault go away,
> and it's clearly an unacceptable hack.
>
> I've attached the following:
>   details.txt-- detailed problem description
>   echomsg.tar.gz -- a simple example
> details
>
> Any help in correcting/understanding this will be appreciated.
> Sorry for the size of this post, but I'm trying to provide all
> of the details necessary to resolve this.  Thanks,

The problem is that there are class conflicts, as half of the SOAP classes
are in the webapp CL, and will be loaded from there (since the CL won't
delegate), and the rest will be loaded from the shared CL. The conflicts
will occur because the SOAP classes loaded from the shared CL will also load
a "different" copy of the same SOAP classes from soap.jar.

Moving soap.jar to $CATALINA_HOME/webapps/soap/WEB-INF/lib/soap.jar should
solve the problem, and could be used as a workaround. Alternately, you can
remove from $CATALINA_HOME/webapps/soap/WEB-INF/classes/ the classes which
are also present in the JAR.

Note: I don't consider this a Catalina problem, but more a questionable
packaging choice of the SOAP binary.

Remy


--
To unsubscribe, e-mail:   
For additional commands, e-mail: