I really don't have time for a full refactoring on this project right
now, but I got this going with a minor one. When I looked more closesly
at it, there was only one method in the equipment classes that was using
the servlet API, so I was able to rework that method and the place from
which i
Thanks for the suggestion!
David Smith wrote:
The easy way in my opinion is to abstract the common stuff to a
superclass and then subclass to servlet vs. standalone. The servlet
subclass goes in WEB-INF/lib, the standalone subclasses can be in the
standalone application jar.
--David
Da
The easy way in my opinion is to abstract the common stuff to a
superclass and then subclass to servlet vs. standalone. The servlet
subclass goes in WEB-INF/lib, the standalone subclasses can be in the
standalone application jar.
--David
David Kerber wrote:
David Smith wrote:
JAVA_HOME/
David Smith wrote:
JAVA_HOME/lib/ext is in the bootstrap classloader (top-most, above
System). Given your need for running this code standalone and in a
webapp, I think a refactoring is in order. The parts that have to
live in JAVA_HOME/lib/ext should not refer to the servlet api. They
sho
JAVA_HOME/lib/ext is in the bootstrap classloader (top-most, above
System). Given your need for running this code standalone and in a
webapp, I think a refactoring is in order. The parts that have to live
in JAVA_HOME/lib/ext should not refer to the servlet api. They should
just return data
And where is the class that can't find HttpServletRequest? If in the
common/endorsed folder, try moving it to your WEB-INF/lib (just to test
a theory). I suspect your startup parameters essentially added the
common/endorsed folder to the system classloader which puts it above the
common classload
I did some more testing, and discovered an error in my OP. See inline
below...
I already have a message into the makers of the jni package I'm using
with my standalone app to see if they have any input on this.
David Smith wrote:
And where is the class that can't find HttpServletRequest?
Hi David,
On 4/19/07, David Kerber <[EMAIL PROTECTED]> wrote:
Check if you have servlet-api.jar in:
C:\Program Files\Apache Software Foundation\Tomcat 5.5\common\lib\
Running tomcat 5.5.15 on Windows server 2003.
Why would I get the subject error when I'm deep into my code, and not
near the t
Running tomcat 5.5.15 on Windows server 2003.
Why would I get the subject error when I'm deep into my code, and not
near the top when I first use it? I'm getting this in a class that is
buried several layers deep in a utility jar file. The servlet that
calls this class is working fine, I get
