What I use on my systems is to define xml-Entities for the components that I
want common to my webapps.
"BOULAY Arnaud" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Ok, thanks !
but what about commons tips (like timeout) : one web.xml for many web apps
implies
ULAY Arnaud [mailto:[EMAIL PROTECTED]
>Sent: Friday, June 06, 2003 11:25 AM
>To: Tomcat Users List
>Subject: Re: RE: one web.xml for many web apps
>
>Ok, thanks !
>but what about commons tips (like timeout) : one web.xml for many web apps
>implies the same session timeout for al
Ok, thanks !
but what about commons tips (like timeout) : one web.xml for many web apps implies
the same session timeout for all of them: its a technical limit.
Regards,
Arnaud
Messages d´origine
De: "Shapira, Yoav" <[EMAIL PROTECTED]>
Date: Vendredi 6 Juin 2003
8:05 AM
>To: [EMAIL PROTECTED]
>Subject: one web.xml for many web apps
>
>Hello !
>It is said in Struts doc that only one controler servlet garantees that
all
>will work fine but I must specify many web app in one descriptor (so
many
>"Action Servlet" in 1 web.xml ) so
Hello !
It is said in Struts doc that only one controler servlet garantees that all will work
fine but I must specify many web app in one descriptor (so many "Action Servlet" in 1
web.xml ) so what is the real risk ? and the limitations ?
I think that it's not a good idea but I must proove it to
