[prev in list] [next in list] [prev in thread] [next in thread] 

List:       james-dev
Subject:    Re: Remove phoenix-deployment in favor of use pure Spring based
From:       Robert Burrell Donkin <robertburrelldonkin () gmail ! com>
Date:       2009-12-27 18:42:27
Message-ID: f470f68e0912271042j1dadedf4m5d2c0a3d0e1ecede () mail ! gmail ! com
[Download RAW message or body]

On Tue, Dec 22, 2009 at 10:52 AM, Norman Maurer <norman@apache.org> wrote:
> Hi all,
>
> as you all prolly know I tried to decouple james in the last couple of
> weeks from phoenix / avalon as much as possible. This task is now
> complete and James should "just work" within every container /
> framework which understand howto handle jsr250 injections. I thought
> about using OSGI + Karaf as container for James but I think that would
> require many reorganisation within the code to get it work like it
> should. So while using OSGI is prolly not the worst move to attract
> more users / developers I'm still not 100 % sure if its really a good
> idea at all.
>
> At the moment I tend to just remove the Avalon-Guice Adapter classes
> which I create for every component and let just handle spring the
> injection stuff. The Log and Configuration injection will get done via
> Spring by using a BeanPostProcessor (like its done in the current
> spring-avalon-bridge).
>
> So anyone against this "radical" move ?

the karaf stuff has always been orthogonal to spring-avalon as far as
i was concerned. it's a very capable OSGi container but james needs an
injection container to assemble the components anyway.

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]