Newbie question here...
The development and production jsp/templates for the application I'm
working on have historically been separate. The development pages are
ugly but guaranteed to work right because the content people never hack
them; the production pages are pretty. The development pages are
maintained in the development CVS; the production pages are handled by
the production people and are not in CVS. Not ideal, but out of my
control.
The old perl-based system determines which template to use via a
database lookup. It's a resource intensive approach but allows stuff
like introducing replacement pages while still keeping the old one as a
fallback, and the production people can do it by themselves. When the
production people have a problem, I can reset the db on the staging
system to point to the 'development' template, and see whether the
problem is in their template or the code that generates perl objects for
the page.
I'm trying to figure out how to model this arrangement in Struts. The
key issue is that there needs to be a completely separate (but parallel)
heirarchy of pages for production use, and those pages have to be
readily changeable without involving development folks in the process.
I'm not even sure I can get those pages into the WAR, since they are
only available on the production machines!
Any ideas on how I should approach the problem?
Thanks!
Gary Shea
GTS Design Consulting
Salt Lake City Utah
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
