Then I would suggest Tiles. This would be as easy as getting wet in a pond.
Scott On Jan 13, 2008 9:01 PM, Neil Aggarwal <[EMAIL PROTECTED]> wrote: > Rod: > > The functionality will be exactly the same for > each site. > > How do I tell struts to load a given set of > tiles based on the domain name? > > Thanks, > Neil > > -- > Neil Aggarwal, (832)245-7314, www.JAMMConsulting.com > Eliminate junk email and reclaim your inbox. > Visit http://www.spammilter.com for details. > > > -----Original Message----- > > From: Rod Bollinger [mailto:[EMAIL PROTECTED] > > Sent: Sunday, January 13, 2008 3:38 PM > > To: 'Struts Users Mailing List' > > Subject: RE: [S2] Best approach to separate look & feel with > > same backend code > > > > Hi Neil, > > > > When you say Look and Feel are you referring to just the > > visual aspects of > > the site or are you referring to a marked difference in front-end > > functionality? > > > > If you are not providing differing functionality or the > > functionality being > > provided is mostly similar to the current site, your best > > approach will be > > to use CSS to make one site look and feel different than the > > other site. > > > > Additionally, if your current site is not already using > > Tiles, you should > > consider refactoring to add this flexibility. With a Tiles > > and CSS-based > > approach you can completely re-use your current middle and > > back-end tiers > > with little or no modification. > > > > You do not need a whole new set of JSPs, simply a flexible > > view structure > > and a well-defined view decoration strategy (Tiles and/or CSS > > to modify > > structure and CSS to modify the presentation). > > > > Lastly, if you are relying on certain behaviors (Javascript), > > these should > > be designed such that they are generic. As such they may be > > applied to one > > or more of your sites independent of the structure and > > presentation of a > > given site. > > > > The only reason you would need an entirely different set of > > JSPs would be if > > they were providing a completely different application of the > > underlying > > information (back-end). As there should be no business or > > control logic in > > your JSPs, I still would think about the above approach > > before taking such > > drastic measures as re-creating everything. > > > > HTH, > > -Rod > > > > > > -----Original Message----- > > From: Neil Aggarwal [mailto:[EMAIL PROTECTED] > > Sent: Sunday, January 13, 2008 14:05 > > To: user@struts.apache.org > > Subject: [S2] Best approach to separate look & feel with same > > backend code > > > > Hello: > > > > I am trying to figure out the best way to do this: > > > > I have two domains. > > > > I am going to develop two different web sites > > which will use the same backend database and have > > the same functionality, just a different look and > > feel. > > > > Should I: > > > > 1. Create two separate webapps? That seems poor > > since there will be a lot of duplicated code. > > > > 2. Create one webapp and pass around a site identifier? > > Then, I can load the correct set of JSPs based > > on the identifier? > > > > Any suggestions for the best way to do this? > > > > Thanks, > > Neil > > > > -- > > Neil Aggarwal, (832)245-7314, www.JAMMConsulting.com > > Eliminate junk email and reclaim your inbox. > > Visit http://www.spammilter.com for details. > > > > > > --------------------------------------------------------------------- > > 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] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Scott [EMAIL PROTECTED]
