I'm currently setting up our team environment to use the sub projects. But a question I have is this, are the jsp blind to this shift in the configuration files? Basically, so I need to change the paths or anything in the jsp files to know that it should be pointed to a specific config file? I wasn't under the impression that I did, but when I try to implement this, the action isn't finding the path. It says "invalid path" and display the path I'm trying to invoke. So I'm not sure where the disconnect is happening. When starting up my server it loads the Resources file, so it's finding it in the file. Any suggestions?
Thanks! Steven -----Original Message----- From: Joe Barefoot [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 2:26 PM To: Struts Users Mailing List Subject: RE: multiple sub projects > -----Original Message----- > From: Taylor, Jason [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 26, 2002 11:28 AM > To: 'Struts Users Mailing List' > Subject: RE: multiple sub projects > > > My interest in multiple sub-apps is more related to maintenence and > post-launch life cycle issues. > > Modular development is nice, but to me fine-grained control > of override > behavior for every aspect of the deployed application is > crucial-- that way > I can add functionality or upgrade any feature of an > application without > touching any of the original version's code/media/configuration, while > keeping it all in one deployment unit. I'm not following you here...do you mean that it's easier because you only have to upgrade the sub-app for which you are making upgrades? > > This makes it possible to more organically migrate (or > rollback) from one > version to another. It also reduces the amount of duplicated > code/JSPs/media/etc drastically when closely similar versions > can share > things. Also not following you...how does having multiple sub-apps reduce duplicated code/JSPs? > > -----Original Message----- > From: Joe Barefoot [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 26, 2002 10:20 AM > To: Struts Users Mailing List > Subject: RE: multiple sub projects > > > Pardon me if this questions seems a bit daft, but what does > using multiple > sub-applications buy you other than splitting the app. into > logical chunks, > each with its own config file? > > > -----Original Message----- > > From: Eddie Bush [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, September 26, 2002 10:23 AM > > To: Struts Users Mailing List > > Subject: Re: multiple sub projects > > > > > > I believe what you're trying to do is covered by the > contextRelative > > attribute of the forward. Have you tried setting > > 'contextRelative="true"' on a forward? What it does is tell Struts > > "Interpret this as though it's relative to the APPLICATION > > context (not > > module context)". I know this works for global forwards, and > > I believe > > it would also work for a local one. Note that by specifying > > contextRelative="true" you must provide a path which is, in fact, > > relative to the application and not the module :-) > > > > Anthony Martin wrote: > > > > >What about situations where a common .jsp file is used as a > > target for > > >forward by multiple sub-applications? > > > > > > > -- > > Eddie Bush > > > > > > > > > > -- > > 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
