i've also chosen Hivemind and T5 IoC because of autoloading and because of contributions/configurations.
finer control is ok for me as long as autoloading is default and as i don't have to add a @SubModule annotation referencing a class of another library introducing more dependencies. maybe T5 IoC should work on top of OSGi. Along with module handling (autoload, access control) we could take advantage of OSGis runtime behaviour. (Eclipse Equinox does support many of the concepts found in T5 IoC like extension-points and extensions aka. configurations and features an autoload bundle) g, kris Ognen Ivanovski <[EMAIL PROTECTED]> 05.11.2007 09:23 Bitte antworten an "Tapestry development" <[email protected]> An "Tapestry development" <[email protected]> Kopie Thema Re: DISCUSS: Remove Module autoloading On 2007-11-04, at 04:53, Robert Zeigler wrote: > I think autoloading has a lot of merits, and would hate to see it > ripped out. What I /would/ like to see is finer-grained control > over autoloading. For example, a mechanism to specify which > modules should /not/ be autoloaded. +1. Just wanted to write this myself. -- Ognen Ivanovski | [EMAIL PROTECTED] phone +389 -2- 30 64 532 | fax +389 -2- 30 79 495 Netcetera | 1000 Skopje | Macedonia | http://netcetera.com.mk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
