Everything works great and the more we convert to struts, the more we like it. We have one issue though that I just can't seem to find a good solution for.
We have a lot of modules. We try to stick each new section of the site in a new module. If we didn't we'd have way too many action and tile definitions for one xml file. We don't much like the idea of listing multiple struts-config files in the default module and bypassing modules either because then we can't as easily take module and deploy them on other applications.
The problem is starting to arise that we have lots of places in the application that need to be tied together but are in different modules. This always works with links but when a form is involved a tile in one module can't find the form bean of an action that is in another module. I know this is a known issue. I'm just wondering what the best practise would be to get around it.
One thing we have already tried are listing those specific module crossing actions in a "struts-globals.xml" file. Add struts-globals.xml to the web.xml in each module then the action in question is simply defined in all modules. That seems to me like wasting resources a bit though.
Another way might be to make an xml file that just contains a specific action and then to only include that extra xml file within modules that needs the action in question. That seems like it'd get kind of messy after a while too.
So, does anyone have a patch that fixes this? Or has this been changed post 1.1? Any other ideas for getting around the issue?
Comments Appreciated. -Dennis
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
