It's an interesting idea but, of course, where it counts is in service
contributions which already have an ordering mechanism. Also, I don't
think that ordering the entire module is going to be universally
correct for all contributions inside the module.
On Thu, Mar 25, 2010 at 2:07 AM, Robin Komiwes <odiss...@gmail.com> wrote:
> Hi,
>
> I'm pretty sure this already have been suggested, but, why not
> offering the possibility to order Tapestry Modules via annotations on
> Modules classes?
>
> �...@order("before:TapestryModule,after:TapestryIOCModule")
> public class MyModule {
> ...
> }
>
> It would solve lots of problems like service
> instantiation/configuration override ones. Theses problems happens
> often when you want to tweak Tapestry.
>
> The good thing is that it seems also backward compatible.
>
> Regards,
>
> Robin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
