I don't know if this is what you're looking for, but I created an
application that consists of two separate web apps. The first one is a
channel application that handles user interface and basic edits. It
forwards to a second application that has the business logic. The
thinking here is that other channels could share the back-end
application's business logic.

I did this by extending the RequestProcessor to look for a specific
forward name. If it sees "common_" at the beginning, it gets the context
of the backend application and forwards it there. If it sees "reply_" it
pulls some values out of the request to determine to where it should
forward. The channel is responsible for setting these values
appropriately.

Scott Mulligan


-----Original Message-----
From: Craig Edwards [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 12, 2005 4:48 AM
To: user@struts.apache.org
Subject: Framework and application webapps


I have been using struts for a while now and have built up a collection
of  
common code/forms/actions (stuff like log on, log off, administer news  
items, etc).  Everytime I create a new web application that builds on
top  
of these, I seem to be copying all the form/action definitions from my  
framework into the application's code hierarchy (and struts-config.xml).

Ideally, I would like to keep the framework code and form/action  
definitions in my framework WebApp.  Then in my ApplicationX WebApp, I  
somehow reference the framework WebApp and "inherit" the  
tiles/forms/actions.  I know that the web.xml allows me to specify  
multiple struts-config.xml files, but can I get it to work across  
WebApps?  Any pointers or advice would be much appreciated.  Many
thanks.

-- 
Craig Edwards


---------------------------------------------------------------------
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]

Reply via email to