Re: SOAP: Unable to resolve target object

Hi Phil, >Exception in thread "main" java.lang.NoClassDefFoundError: > >I put this /webapps/soap/WEB-INF/classes in the CLASSPATH (in >case). Your client will rely on the CLASSPATH to find its classes (unlike the server which uses TomCat's class loader hierarchy). Whenever I've had problems like

Re: SOAP: Unable to resolve target object

Strange but it doesn't work anymore!!! When I run the client, I have the following (basic!) Exception: Exception in thread "main" java.lang.NoClassDefFoundError: this class is in /webapps/soap/WEB-INF/classes/ The compilation is OK. I put this /webapps/soap/WEB-INF/classes in the CLASSPATH (in

Re: SOAP: Unable to resolve target object

Craig R. McClanahan wrote: > Of course, I also feel that ***way*** too many Tomcat developers and users > put ***way*** too much stock in sharing JAR files, giving up the notion > that a webapp is a stand-alone deployable unit. Very true, but the very presence of $CATALINA_HOME/common, suggests t

Re: SOAP: Unable to resolve target object

>> Craig R. McClanahan wrote: snip > snip >"But wait ... snip >"But wait ... that means snip > > ;-) -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: SOAP: Unable to resolve target object

On Wed, 20 Nov 2002, Glenn O wrote: > Date: Wed, 20 Nov 2002 17:05:23 -0800 > From: Glenn O <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: Tomcat Users List <[EMAIL PROTECTED]> > Subject: Re: SOAP: Unable to resolve target obj

Re: SOAP: Unable to resolve target object

Craig R. McClanahan wrote: > > > > Is anybody else using SOAP and tomcat 4? If so, have you run into a need to > > share classes across contexts, and if so, how did you do it? I'd like to > > improve on my copy-on-startup approach. > > > > In general, it's really easy to share classes across weba

Re: SOAP: Unable to resolve target object

On Tue, 19 Nov 2002, Glenn O wrote: > > Is anybody else using SOAP and tomcat 4? If so, have you run into a need to > share classes across contexts, and if so, how did you do it? I'd like to > improve on my copy-on-startup approach. > In general, it's really easy to share classes across webapps

Re: SOAP: Unable to resolve target object

Hi John, I think I get it! When i unpacked the soap.war file to put my classes in /webapps/soap/WEB-INF/classes/packagename/, I forgot to set the WebAppDeploy to 'soap' in my Apache configuration file ( it was set on soap.war, so the classes could'nt be seen) > > > ConfigFile > /WEB-INF/soap.x

Re: SOAP: Unable to resolve target object

<[EMAIL PROTECTED]> wrote: > >I've also had a problem using SOAP within tomcat. I haven't been able to > >find a way to share the service class files across contexts. > > I did it backwards and put the soap servlet into my context. I can use the > same supporting beans to provide html output for

Re: SOAP: Unable to resolve target object

Hi Phil, >I've also had a problem using SOAP within tomcat. I haven't been able to >find a way to share the service class files across contexts. I did it backwards and put the soap servlet into my context. I can use the same supporting beans to provide html output for humans and soap rpc for mach

Re: SOAP: Unable to resolve target object

<[EMAIL PROTECTED]> wrote: > My situation is complicated because JBoss deploys my webapp afresh every > time TomCat is started and there is no fixed path to my webapp directory, > so any persistent soap deployment info there is lost when the server > is restarted. To counteract this, I put the fol

Re: SOAP: Unable to resolve target object

Hi Phil, >Why put the client classes in TomCat's common/lib directory ??? Sorry, this was bad English on my part. Obviously the client classes go in the (soap webapp's) WEB-INF/classes; whether you put the soap jarfile there or in the common/lib directory depends on whether you want it to be avai

Re: SOAP: Unable to resolve target object

> > Firstly, TomCat ignores your CLASSPATH. The SOAP libraries and your client > classes have to be in TomCat's common/lib directory and your webapp's > WEB-INF/classes directory in order to be found when servicing a request. > Why put the client classes in TomCat's common/lib directory ??? I put

Re: SOAP: Unable to resolve target object

Hi Phil, >I tried to install a SOAP service on an Apache server with Tomcat 4.1 webapp module. > >I deployed the SOAP service with no problem. The SOAP client is well compiled. >But when I run the client, i have the following message: > >Unable to resolve target object : > >CLASSPATH seems well.

SOAP: Unable to resolve target object

I tried to install a SOAP service on an Apache server with Tomcat 4.1 webapp module. (It's a simple Hello 'name' SOAP tutorial example) I deployed the SOAP service with no problem. The SOAP client is well compiled. But when I run the client, i have the following message: Unable to resolve target