technology to
solve business problems on your plant floor.
http://stratuscom.ca
>-Original Message-
>From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Bill Barker
>Sent: November 27, 2002 00:47
>To: [EMAIL PROTECTED]
>Subject: Re: RMI and Tomcat
>
>
>This is starting to look l
This is starting to look like a classic case of bad design. But to get your
app working, try adding servlet.jar to the CLASSPATH of rmiregistry.
"Sarah L. Moore" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Well, I just moved the application classes over to
Well, I just moved the application classes over to the
examples/WEB-INF/classes directory and re-ran my servlet. I get a slightly
different message:
java.rmi.ServerError: Error occurred in server thread; nested exception is:
java.lang.NoClassDefFoundError: javax/servlet/ServletRequest
From th
Sorry, did not correctly see which class it was complaining about. Try
and move MyApplicationStarter to the said directories.
Sarah L. Moore wrote:
Thanks for your reply. My servlet class is in
examples/WEB-INF/classes. If I comment out the RMI step, the servlet
runs fine, so I'm left to thi
Thanks for your reply. My servlet class is in
examples/WEB-INF/classes. If I comment out the RMI step, the servlet runs
fine, so I'm left to think that the servlet location, etc. are OK, but
something relating to RMI is the culprit.
At 11:01 AM 11/27/2002 +0800, you wrote:
" Cannot allocate s
" Cannot allocate servlet instance for path /examples/servlet/MyServlet
" means that it can't find the requested servlet for that web app which
implies that your servlet class isn't where it should be. Servlets &
classes go in /examples/WEB-INF/classes or
/examples/WEB-INF/lib for jar packages.
> I have made two posts to the list about similar problems with 3.2.1 and
> using JNDI/RMI (EJB's) and not figured much out. Not having the time to
> delve further I backed off to Tomcat 3.1. You may try that for the
interim.
> Any feedback from any of the implementors that would help us start to
I have made two posts to the list about similar problems with 3.2.1 and
using JNDI/RMI (EJB's) and not figured much out. Not having the time to
delve further I backed off to Tomcat 3.1. You may try that for the interim.
Any feedback from any of the implementors that would help us start to figure
t
