On Wed, 17 Oct 2001, Firestar wrote:
> Date: Wed, 17 Oct 2001 20:52:20 -0700 (PDT)
> From: Firestar <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: RE: How to change session key name
>
> But JRun does allow me to change it:) I was hoping
> Tomcat 4.0 would be as flexible...
>
And I was hoping that you recognized how badly serverd your employer is
(by those who developed this application) if your application depends on
something as obscure as this. The *right* behavior would be to change
your app so that you are not locked in by it.
> For e.g. another gd thing abt JRun is that it allows
> us to place our servlets and classes anywhere, instead
> of WEB-INF folder.
It is not defined in the spec (unlike the name of the sesson id cookie :-)
so servers can do what they want in this respect. And Tomcat 4
automatically adds any JAR files in $CATALIAN_HOME/common/lib and
$CATALINA_HOME/lib to the set of classes visible to webapps. On
Unix-based systems, you can create symbolic links to the existing JAR
files so that they don't have to be moved.
On any platform, you can modify the startup scripts to set the CLASSPATH
variable differently -- but you're on your own for dealing with the
problems this will cause (which is why CLASSPATH is ignored in the
standard startup script).
> Specification or not, there are
> times where due to certain reasons or legacy issues
> internally, we have to break the 'rule'. And so far we
> still can't move to Tomcat, as much as we would like
> to...:(
>
So who's fault is that? It's not Tomcat's fault that you locked yourself
in to something like this. And if you had started started on Tomcat and
locked yourself in to it by depending on a Tomcat-specific feature, I
would be just as disappointed.
PLEASE do yourself and your employer a favor, and pay attention to what's
important here!
> Firestar
>
Craig
