The intention ( in tc3.3 ) is to make all the configurations "explicit",
instead of using conventions like "webapps will be in home, libs in
install, etc".
Even in 3.2 we tried to allow a shared installation dir and multiple
work dirs ( i.e. you have one tomcat installed in /opt/tomcat, and
Costin - Thanks a ton for your reply. Very helpful.
--- [EMAIL PROTECTED] wrote:
The intention ( in tc3.3 ) is to make all the
configurations "explicit",
instead of using conventions like "webapps will be
in home, libs in
install, etc".
This sound great. I am a big proponent of
In 3.3, the logs are corectly set relative to
TOMCAT_HOME.
and should be implicitely written to paths relative to
the application 'home', not into TOMCAT_HOME. This
is simple OO partitioning of responsibilities.
Ok, this is a clear example of what's wrong with the current
status -
No need, it's already done ( and in 3.2 too ).
( I have no idea who did it - it's not me, and I was
quite surprised to find it there :-)
Erggg, hummm, i did from code of Alex Chafee, it was inadvertly slipped
in a commit many time ago ( about August or Sept ) , but it's truly
useful :) so
--- [EMAIL PROTECTED] wrote:
Ok, this is a clear example of what's wrong with the
current
status - there are 2 directories that can be set on
ContextManager,
one is "home" and the other one is "installDir".
The env. variable is used to set home.
Where is this stuff documented? There
status - there are 2 directories that can be set on
ContextManager,
one is "home" and the other one is "installDir".
The env. variable is used to set home.
Where is this stuff documented? There doesn't seem to
be a DTD for server.xml.
It's still on the TODO list, but it'll happen
--- [EMAIL PROTECTED] wrote:
No, the overhead of using a servlet to invoke the
jsp page is significant ( at least in my tests
is shows a big difference ).
JspInterceptor does a simple thing - after the
jsp page is compiled to a servlet, the servlet
will be "registered" to tomcat ( as
