Hi David,
I did a similar project as few months back where we supported 15 different URL
with one Enterprise Implementation. The FilterDispatacher approach I guess is
the right way to modularize the code.
Your own FilterDispatacher (extending the Struts FilterDispatcher this class),
which parses the URLs and redirected/forwarded the calls to the main
application action classes. In this class you can also enforce other rules.
Example :
-- Mandating usage of "https" if the user types "http"
-- Can handle application level controls Language and other stuff.
Hope it helps.
regards
Kishore.
________________________________
From: David Canos <davidca...@gmail.com>
To: Struts Users Mailing List <user@struts.apache.org>
Sent: Thursday, July 30, 2009 4:39:11 PM
Subject: One Struts2-project to rule them all
Hi folksI'm facing a nice problem and I would be glad to hear from you. I
think it should be useful to all.
Problem is easy:
Gandalf and I need to build 15 websites one per domain, I really dont want
to maintain 15 different and pretty small projects.
I will be happy to use subdomains, but I couldnt.
Alternatives:
- A Struts2 project attending 15 websites.
is it possible? Writing my own FilterDispatcher??
- Multiple Struts2 project on per domain bundled in a EAR.
I think I will overhead the job.
I dont want to duplicate struts configurations, javascript and
css resources.
