Re: RE: one web.xml for many web apps

2003-06-07 Thread Bill Barker
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 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 14:13
Objet: RE: one web.xml for many web apps


 Howdy,
 There is one deployment descriptor per web application.  This
 deploymentdescriptor is web.xml.

 Struts lets you define many sub applications or application flows
 (which translate into struts controller servlets) in every web
 application.

 The question is whether these application flows are big enough /
 complexenough / loosely coupled enough (this last one is often the
 key) to be
 webapps by themselves.

 Yoav Shapira
 Millennium ChemInformatics


 -Original Message-
 From: BOULAY Arnaud [EMAIL PROTECTED]
 Sent: Friday, June 06, 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 what is the real risk ? and the
 limitations ?
 I think that it's not a good idea but I must proove it to my
 customer.Thanks in advance.
 Arnaud
 
 
 
 --
 ---
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




 This e-mail, including any attachments, is a confidential business
 communication, and may contain information that is confidential,
 proprietary and/or privileged.  This e-mail is intended only for
 the individual(s) to whom it is addressed, and may not be saved,
 copied, printed, disclosed or used by anyone else.  If you are not
 the(an) intended recipient, please immediately delete this e-mail
 from your computer system and notify the sender.  Thank you.


 ---
 --
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: one web.xml for many web apps

2003-06-06 Thread Shapira, Yoav

Howdy,
There is one deployment descriptor per web application.  This deployment
descriptor is web.xml.

Struts lets you define many sub applications or application flows
(which translate into struts controller servlets) in every web
application.

The question is whether these application flows are big enough / complex
enough / loosely coupled enough (this last one is often the key) to be
webapps by themselves.

Yoav Shapira
Millennium ChemInformatics


-Original Message-
From: BOULAY Arnaud [mailto:[EMAIL PROTECTED]
Sent: Friday, June 06, 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 what is the real risk ? and the
limitations ?
I think that it's not a good idea but I must proove it to my customer.
Thanks in advance.
Arnaud



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: RE: one web.xml for many web apps

2003-06-06 Thread BOULAY Arnaud
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 14:13
Objet: RE: one web.xml for many web apps

 
 Howdy,
 There is one deployment descriptor per web application.  This 
 deploymentdescriptor is web.xml.
 
 Struts lets you define many sub applications or application flows
 (which translate into struts controller servlets) in every web
 application.
 
 The question is whether these application flows are big enough / 
 complexenough / loosely coupled enough (this last one is often the 
 key) to be
 webapps by themselves.
 
 Yoav Shapira
 Millennium ChemInformatics
 
 
 -Original Message-
 From: BOULAY Arnaud [EMAIL PROTECTED]
 Sent: Friday, June 06, 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 what is the real risk ? and the
 limitations ?
 I think that it's not a good idea but I must proove it to my 
 customer.Thanks in advance.
 Arnaud
 
 
 
 --
 ---
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 This e-mail, including any attachments, is a confidential business 
 communication, and may contain information that is confidential, 
 proprietary and/or privileged.  This e-mail is intended only for 
 the individual(s) to whom it is addressed, and may not be saved, 
 copied, printed, disclosed or used by anyone else.  If you are not 
 the(an) intended recipient, please immediately delete this e-mail 
 from your computer system and notify the sender.  Thank you.
 
 
 ---
 --
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: RE: one web.xml for many web apps

2003-06-06 Thread Shapira, Yoav

Howdy,
If you need different sub-applications to have different session timeouts, I'd say the 
sub-applications are different enough to be their own web applications, each one with 
their own web.xml.

Yoav Shapira
Millennium ChemInformatics


-Original Message-
From: BOULAY 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 all of them: its a technical limit.
Regards,
Arnaud


 Messages d´origine 
De: Shapira, Yoav [EMAIL PROTECTED]
Date: Vendredi 6 Juin  2003 14:13
Objet: RE: one web.xml for many web apps


 Howdy,
 There is one deployment descriptor per web application.  This
 deploymentdescriptor is web.xml.

 Struts lets you define many sub applications or application flows
 (which translate into struts controller servlets) in every web
 application.

 The question is whether these application flows are big enough /
 complexenough / loosely coupled enough (this last one is often the
 key) to be
 webapps by themselves.

 Yoav Shapira
 Millennium ChemInformatics


 -Original Message-
 From: BOULAY Arnaud [EMAIL PROTECTED]
 Sent: Friday, June 06, 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 what is the real risk ? and the
 limitations ?
 I think that it's not a good idea but I must proove it to my
 customer.Thanks in advance.
 Arnaud
 
 
 
 --
 ---
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




 This e-mail, including any attachments, is a confidential business
 communication, and may contain information that is confidential,
 proprietary and/or privileged.  This e-mail is intended only for
 the individual(s) to whom it is addressed, and may not be saved,
 copied, printed, disclosed or used by anyone else.  If you are not
 the(an) intended recipient, please immediately delete this e-mail
 from your computer system and notify the sender.  Thank you.


 ---
 --
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]