Or did you mean I'm not modularizing my app well? Maybe so, but I still think a notion of a Struts "application" could be beneficial.
No, I meant nothing like that.
IMHO, the conceptual issue is that there seems to be no notion of a Struts "application" reflected in the code because all the modules are peers with equal status.
I'm pretty sure this was an explicit design intention, although the main reason may have been to make backwards compatibility more manageable (or maybe not -- I can't cite any place where this was discussed; I just have vague recollections). From reading the lists, it's clear that many people intuitively expect modules to be less walled off from each other.
Maybe a smarter Modularization, but one which might break some compatibility, could be targetted for a 1.5 release, or some mid-point between 2.0, which has a lot of bigger changes marked for it.
Or maybe compatibility can be preserved anyway.
Joe
--
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "If nature worked that way, the universe would crash all the time." --Jaron Lanier
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
