Wouldn't it be better to describe the interdependencies of the plug-ins and let struts build a directed graph to automatically load them in the proper order. Otherwise, someone is going to put plugin1 at order=5 and plugin2 at order=6 then plugin3 will come along and need to be in between. There would no reason that the dependencies would "have" to be requirements, some of the dependencies could be "soft" (i.e. If the spring libraries are available, they're a soft dependency of struts, meaning they should be loaded first). Then you would have something more like this:
In convention: <dependencies> <dependency optional="true">OSGi</dependency> <dependencies> (*Chris*) On Sat, Apr 4, 2009 at 6:50 PM, Musachy Barroso <musa...@gmail.com> wrote: > I have been trying a few different ways to get the Convention plugin > to work with the OSGi plugin, and there are some hacks that can be > done but I don't like them. I want to implement (I actually have it > implemented it already somewhere) a simple way for the config files to > specify a relative order of loading. This way I can at least make sure > that certaing plugins are loaded before others. It would look like > this in the xml: > > OSGi: > <struts loadOrder="10">...</struts> > > Convention: > <struts loadOrder="20">...</struts> > > With this in place, we can enable some sort of communication between > plugins, by adding common interfaces to core. Any thoughts? > > musachy > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
