>>>>> Steinar Bang <[EMAIL PROTECTED]>:
> What I would like to do is to custimize installations of a
> struts-based web application, in a way that isn't overwritten when a
> new version of the webapp's .war file is installed.
[snip!]
> Ie. have a search path for the JSPs?
> Other ideas I have considered, are:
[snip!]
Here's my current best idea:
- Don't use a .war for the webapp. Deliver the webapp with an RPM
that uses a directory out of tomcat's normal hierachy, and change
server.xml to add a context for this directory
- Subclass ActionServlet and replace the function that adds the
action mapping (seems to be actionMapping() in 1.0, but that
function was gone in HEAD), to first do a
super.initMapping();
and then read action configs from the database, potentially
replacing the actions set by struts-config.xml
Instead of creating JSPs with identical names that are picked before
the standard JSPs, new JSPs will be created with different names, or
put in a separate subdirectory, and actions forwarding to these JSPs
will be put into the database.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
