Brett,
In order to make this class available through SOAP, it needs to be in the
startup classpath. I have asked this question already about 3 times since
I had the impression that I could package my SOAP app in a war file and just
drop it in tomcat/webapps in order to make it work. Unfortunately, this is
not the case. I havent gotten a clear answer as to why. So, in short, you
need to have that class available through tomcats' startup classpath,
otherwise, you will get a ClassNotFoundException thrown when the servlet
tries to load it. I even looked at the code that does this. It looks correct
in that it is asking for the servlet class loader for the class you're
invoking, however, it still doesnt work. Any clarification on this is
welcomed.
thanks,
-javier
Brett McLaughlin wrote:
> Simple question I didn't see a clear answer to.
>
> I have a set of code artifacts for the server to expose through SOAP-RPC.
> Say, a class called CDCatalog in the javaxml2 package (so
> javaxml2.CDCatalog). I've got my deployment descriptor all set up, and
> registered with the server. My question is where does that class (and its
> supporting classes) need to be in relation to Tomcat, my servlet engine?
> Obviously Tomcat needs to find them; and I don't just want to hardcode the
> path to them in my startup.bat or anything silly like that.
>
> Thanks for the help,
> Brett
