Hello, I generally create a WebApp directory that uses symlinks to reference
all the top level JSP directory trees in my WebApp. I do this so I can have
a
single JSP source tree in multiple App Server instances. With Tomcat 4.1 I
am
forced to add a Resources element to the Context definition to get JSP pages
to
compile. My Resources entry in my server.xml looks like this:
<Resources
className="org.apache.naming.resources.FileDirContext"
allowLinking="true"
docBase="/home/mikem/web/tomcat-4.1/SPRTmikem" />
Here SPRTmikem is the root directory of my Web App. This allows the JSPs to
compile, but if I hit a page referenced through a symlink I get a new
Session
object with every page hit. For example if I have two directories under
SPRTmikem called symtest and phystest each with a sesstest.jsp file in them,
and symtest is a symlink to a directory outside the SPRTmikem web app
directory
each time I hit /SPRTmikem/symtest/sesstest.jsp I get a new Session object.
If I
hit /SPRTmikem/phystest/sesstest.jsp the request.getSession() function
behaves as
expected.
This seems like a bug, and I'm willing to track it down if someone knows a
good
place to start looking in the code. Of course if there is a configuration
setting
to correct the problem that would be a lot easier. Does anyone have any
clues?
--MDM
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
