struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hubert Rabago <>
Subject Re: Why I Hate Struts Modules
Date Wed, 12 Oct 2005 16:09:03 GMT

You can declare something like a struts-config-common.xml which will
contain the config items that are common among your modules and then
include them in your config declarations:

<param-name>config</param-name >
<param-name>config/module2</param-name >
<param-name>config/module3</param-name >


On 10/11/05, Paul Benedict <> wrote:
> Great subject line, isn't it? :)
> OK. I've been doing Struts for like 2-3 years now, and
> Struts Modules I loved for awhile but now I absolutely
> can't stand them....
> First off, my initial appeal to modules was to split
> up the configuration files so different developers can
> work on the project without people waiting for
> check-outs. That sounds like a good deal, but Modules
> are MORE than splitting up configuration files - they
> are these Berlin Walls kind of construction where
> forms and actions can't be shared across them ....
> unless you want to define them in multiple config
> files.
> See, after all these years, I really wanted was to
> split files up. Modules don't gain me anything, do
> they? I know (or I think) when Craig wrote Struts 0.x,
> he had an action.xml which did something similar....
> Now I could create file of just actions and use XML
> ENTITIES to include them, but I never see people doing
> that solution. Is it not well-known or frown upon?
> So I am kind of sick of Struts modules. More so, now
> that I have to declare my Struts global exception
> handler in every config file!! This gets ridiculous
> after 5 modules... and forget about it if you have a
> project with 50 modules.
> Too much configuration duplication.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message