[EMAIL PROTECTED] wrote: > The subdirectory idea is one of the ideas I'm working through, although in > a slightly different form from what you describe. For example, one idea > would be to have a directory that contains all the Struts config files for > each plugin. I like this much better than the proposed scheme of > comma-separated file names in the Struts config file, because now my > installer only needs to drop a new config file in the right directory, and > it will be picked up and parsed automagically. Even better, my uninstaller > only has to delete that file, rather than modify a file that another > installer may have modified since its corresponding install.
That's sounds exactly like what I ~meant~ ;-) What this becomes is a strategy for deploying Struts applications as "portlets". The current design brings us within a hairs-breadth of this, we just have to work around some relatively minor configuration issues and adopt a few development conventions. So, we point the digester at some folder, like WEB-INF/struts-config/*, and have it parse whatever is there? Or, do we need Servlet 2.3 for that? > Right. And I'd like to go one step further, if possible, and find a way to > do this without even having to modify the original Struts config file for > the overall app. Perhaps it should be a two-step process. First the configuration is digested, and then merged with any other configuration already loaded. This way we don't have to dance around the XML validation. It would also give us a place to scan for any conflicts. > If we modify the DTD, we might also want to think about moving some of the > init-param entries into the config file. Since we would be freed from the > restrictions of the web.xml DTD at that point, we'd have more flexibility > to do things like adding multi-valued parameters. For example, you might be > able to specify multiple resource file names as separate value elements for > the same parameter name, again getting rid of the need for comma-separated > values. Allowing init-param's in the config is a fine idea. But what I was thinking (above) is that each "sub-directory" could have its own resource file, and that it would prefix each token with the directory name, as the ActionMappings would also be prefixed, to avoid collissions. The resources and other other configurations (like validation.xml) are tightly coupled, and should be considered part of a greater whole. > -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/struts/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
