How to configure Tomcat to provide codebase property for RMI?

[Andrey Karachoun]

Hi
I encountered a problem when using dynamic copying of RMI/JRMP classes and trying to configure Tomcat (4.0.4) to create a codebase for that.
So, I created a new HTTP connector and context path for my application in server.xml file:

<Service name="Tomcat-Standalone">
...
<Connector className="org.apache.catalina.connector.http.HttpConnector" port="2001" minProcessors="5" maxProcessors="75" enableLookups="true" redirectPort="8443" acceptCount="10" debug="0" connectionTimeout="60000"/>
...
<Host name="localhost" debug="0" appBase="webapps" unpackWARs="true">
...
<Context path="/myapp" docBase="myapp" debug="0" privileged="true"/>
...

Application class files are stored in
C:\Tomcat4\webapps\myapp\WEB-INF\classes folder
Run the application with following system property: -Djava.rmi.server.codebase=http://localhost:2001/myapp\WEB-INF\classes
Finally, when trying to create an instance of Remote class, I get the following exception:

 
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: 
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: 
java.lang.ClassNotFoundException: org.myapp.server.session.RemoteSessionImpl_Stub

But I'm sure that I have stubs generated and stored in proper location, so the problem appears to be in invalid configuraion of Tomcat.
Does anybody know what I'm missing? Your help is greatly appreciated.
Andrey
[ January 24, 2003: Message edited by: Andrey Karachoun ]
[ January 24, 2003: Message edited by: Andrey Karachoun ]

[Andrey Karachoun]

Folks, does anybody know?
My problem is: when I used ClassFileServer from Java examples listening on port 2001 my codebase worked fine; when I started using and configuring Tomcat I began getting that java.rmi.ServerException: nested exception is:
java.rmi.UnmarshalException: nested exception is:
java.lang.ClassNotFoundException: *_Stub
My class files and generated stubs are in WEB-INF folder. I've heard that Tomcat protects this folder from accessing by web - could this be the reason that caused the exception?