If the use of modules is truly to split struts-config.xml files, then isn't it simpler to just use comma delimited configuration files in web.xml?
Well... yes. Some times you just do things the way you've always done them until someone points out a good alternative.
Actually, on a current project, we're using modules for more than that, but still don't have the sense of strict compartmentalization that comes with the original module design. The multiple modules is mostly just a way to have multiple "unknown" action configs -- we might be able to use the relatively new wild-card mappings along with a list of config files to get what we need, but this is a temporary approach for prototyping, so it will probably be moot sooner than later.
I still wouldn't mind someone's description of a case where strict separation of modules is necessary, just so I'll recognize it if I ever come across it myself. Maybe it's just a matter of taste, as I prefer to build for permissiveness than restriction (as noted in the other thread about requiring form beans for the html:form tag.)
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining."
-- Jef Raskin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
