<snip> On Mon, Aug 17, 2009 at 10:57 AM, Norman Maurer<[email protected]> wrote: > btw do you already have some idea about how this will work ? I saw you > already created the sandbox :)
i've been taking a look at guice and remembering the problems in the current james code base complete replacement of avalon by guice is going to be a lot of work for a number of good reasons james has coupling issues at the component and service levels. i don't think that these can be solved by guice, and the guice module system may well be difficult to use as a service replacement until they are resolved. i started looking at guice in the sandbox but re-started working on these problems (again). i think it's probably better to sort these issues out on trunk. i wonder whether it might be better to start by taking on something more modest: replacing the ad hoc classloading for handlers and mailets with an injection service. i think that PhoenixLoader could be used to dynamically bind the services started by phoenix into a guice module. guice could then to used to load mailets and handlers injected with the services exposed by phoenix plus any other modules loaded. the injection service would be used as a bridge between the service locator mechanism used by avalon and dependency injection. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
