I developed a system that handles the need for having multiple components of a Struts application (Struts, Tiles, Validator, etc) partitioned in a modular fashion, so that independent groups could work on their component parts without having to worry about what other groups were doing, and yet allow for seamless integration of these components at web application assembly time.
It was a requirement that all of this be done without requiring modification to Struts proper, so this is an approach that can be layered on top of a basic Struts implementation. I had wanted to bring this up a week or so ago when Eddie was talking about this topic, but was too busy then. The basic approach is to define a mechanism which allows module authors to work on individual modules using "fragments" which are then assembled into the final Struts files by Ant. The fragments are XML files which are essentially well-formed versions of the corresponding Struts files. The Ant process uses some style sheet tricks to collect the set of fragments, coalesce the relevant portions of the files into the proper sections (action-mappings, form-beans, etc) in the target XML files (mostly struts-config.xml needed this coalescing). Identifier collisions were avoided by a identifier prefixing scheme where each module would have it's own prefix. If there's interest in examining this approach, I can go into more detail about its operation. It worked well for us, and seems to fit the bill for a way to address the need for modular but not totally independent web applications. Steve > -----Original Message----- > From: Ted Husted [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 16, 2002 1:34 PM > To: Struts Developers List > Subject: Re: Tiles Refactorings for 1.1 compatability > > > 10/16/2002 4:03:01 PM, "V. Cekvenich" > <[EMAIL PROTECTED]> wrote: > >Can you wait till 1.2 Ted? > > All that I'm saying is that we should support specifying a > list of struts-config files, as we do for the > validator and tiles configs. This way people could split up > the config files without buying into modules. Craig > wanted to pursue modules to support URI-independance, but now > that we done that I think we should support the > obvious solution too. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
