On Tue, 7 Jan 2003, Prakash 'pk' Trivedi wrote:
> Date: Tue, 07 Jan 2003 23:00:18 -0500 > From: Prakash 'pk' Trivedi <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: Struts Users Mailing List <[EMAIL PROTECTED]> > Subject: RE: Override action in multiple struts-config.xml > > > A follow up question is so in 1.0.2 or prior to 1.1b3 you just have to merge > them in to a single config file. Yes, although with any 1.1 release you can subdivide your app into separate modules (with their own config files). However, the question that started this thread was about subdividing a struts-config.xml file for a single module -- which is now possible in 1.1b3 but was not before. > Also, if you have multiple struts apps > could you share session among them. We have to be precise about the terminology here. If you divide your app into several Struts *modules* (used to be called sub-applications), you can run them within a single web application, and therefore share sessions. If you put each of your Struts-based apps into a separate web application, sessions will not be shared. > > Thank you, > ~~~~~~~~~~~~~~~~~~~~~~~~~ > Prakash 'pk' Trivedi > ~~~~~~~~~~~~~~~~~~~~~~~~~ Craig > > -----Original Message----- > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 07, 2003 3:24 PM > To: Struts Users Mailing List > Subject: Re: Override action in multiple struts-config.xml > > > > > On Tue, 7 Jan 2003, Michael Lee wrote: > > > Date: Tue, 7 Jan 2003 14:29:30 -0500 > > From: Michael Lee <[EMAIL PROTECTED]> > > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > > To: Struts Users Mailing List <[EMAIL PROTECTED]> > > Subject: Override action in multiple struts-config.xml > > > > We have a base product. It has a struts-config.xml in a webapp. We have > > a couple of customers that each have their own web app and > > struts-config.xml. Their product sits on top of the base product. We > > have to have a complete struts-config.xml for each customer. Is there a > > way to have a core struts-config.xml in the base product and a > > struts-config.xml for each customer where the struts-config.xml for each > > customer uses whats in the base product and adds new actions or > > over-rides the actions in the base struts-config.xml? > > > > thanks, Mike > > As of 1.1-b3 this is in fact pretty easy to accomplish. The "config" init > parameter can now accept a comma-delimited list of struts config files, > that are processed in turn. So, you could have your customers configure > your basic struts-config.xml file first, followed by one that adds > whatever they need second. > > Craig > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
