The different jvm can be a real headache. Even the same jvm on different
platforms can be a pain. And you have both!
I think it will work but I work on Win and Linux so I can't swear to it. I
know it's the normal way to do it.
Let us know if you need anything more.
Doug
Ben wrote:
I will try
Let me float the problem by you. Maybe I am overlooking something in
the config. We have a hard coded URI that goes
/servlet/com.bo.hsal.HSALServlet?foo (it is in 3rd party software
that we do not have the source for). With the invoker taken out, any
call to /servlet fails because it cannot find a
I added the mapping to the web.xml of the app and it made no
difference. For some reason, it seems to ignore the mapping
completely! I have no idea why it works on Solaris but not on AIX!
Ben Ricker
On Thu, 27 Jan 2005 22:45:02 -0500, Parsons Technical Services
[EMAIL PROTECTED] wrote:
I have
Dear Ben,
Just check the servlet mapping package separator that
you have implemented it in AIX and Solaris.
regards,
Das
--- Flaffer [EMAIL PROTECTED] wrote:
I added the mapping to the web.xml of the app and it
made no
difference. For some reason, it seems to ignore the
mapping
completely!
Let me float the problem by you. Maybe I am overlooking something in
the config. We have a hard coded URI that goes
/servlet/com.bo.hsal.HSALServlet?foo (it is in 3rd party software
that we do not have the source for). With the invoker taken out, any
call to /servlet fails because it cannot find
I have not worked with TC4 but I think your problem is that the mappings for
the servlets should be in the web.xml for the app and not in the general
web.xml. Also when you do the mappings in the app web.xml you do not need
fully qualified paths.
Doug
- Original Message -
From:
