You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Norman Maurer <no...@apache.org> on 2009/12/22 11:52:38 UTC
Remove phoenix-deployment in favor of use pure Spring based
deployment
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 ?
Bye,
Norman
Ps: This would eliminate the use of Guice again too
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Bernd Fondermann <bf...@brainlounge.de>.
Norman Maurer 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 ?
+1
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Tue, Dec 22, 2009 at 10:52 AM, Norman Maurer <no...@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
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Norman Maurer <no...@googlemail.com>.
Good point.. Anyway I think I will start to work on this these days
(in a sandbox) just because I will have some time ;) If others think
it was a bad idea at the end I will be happy to just > /dev/null it
and threat it as an funny experiment ;)
Thx for the input.
Bye,
Norman
2009/12/26 Bernd Fondermann <bf...@brainlounge.de>:
> Norman Maurer wrote:
>> Ok because I didn't hear anything against this route I will go ahead
>> and try to get this stuff done.
>
> Mmmh. I think you should give this another week or so to sink in. For
> example, I am only now checking my email since days. Other might also
> want to join in after the holidays. Collecting some more +1s would be
> much safer.
>
> Bernd
>
>>
>> Bye,
>> Norman
>>
>> 2009/12/22 Dhrubo <dh...@gmail.com>:
>>> Friends,
>>> Move towards pure Spring away from dead frameworks is highly
>>> appreciated. I think the move to a OSGi container may come in next release?
>>> Thanks ...dhrubo
>>>
>>> On Tue, Dec 22, 2009 at 4:22 PM, Norman Maurer <no...@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 ?
>>>>
>>>> Bye,
>>>> Norman
>>>>
>>>> Ps: This would eliminate the use of Guice again too
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>>>> For additional commands, e-mail: server-dev-help@james.apache.org
>>>>
>>>>
>>>
>>> --
>>> Thanks ... Dhrubo
>>> My Book - http://www.apress.com/book/view/1430210095
>>>
>>> My Blog -
>>> http://www.jtraining.com/blogs/blogger/dhrubo/
>>>
>>> LinkedIn - http://www.linkedin.com/in/dhrubo
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-dev-help@james.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Bernd Fondermann <bf...@brainlounge.de>.
Norman Maurer wrote:
> Ok because I didn't hear anything against this route I will go ahead
> and try to get this stuff done.
Mmmh. I think you should give this another week or so to sink in. For
example, I am only now checking my email since days. Other might also
want to join in after the holidays. Collecting some more +1s would be
much safer.
Bernd
>
> Bye,
> Norman
>
> 2009/12/22 Dhrubo <dh...@gmail.com>:
>> Friends,
>> Move towards pure Spring away from dead frameworks is highly
>> appreciated. I think the move to a OSGi container may come in next release?
>> Thanks ...dhrubo
>>
>> On Tue, Dec 22, 2009 at 4:22 PM, Norman Maurer <no...@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 ?
>>>
>>> Bye,
>>> Norman
>>>
>>> Ps: This would eliminate the use of Guice again too
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>>> For additional commands, e-mail: server-dev-help@james.apache.org
>>>
>>>
>>
>> --
>> Thanks ... Dhrubo
>> My Book - http://www.apress.com/book/view/1430210095
>>
>> My Blog -
>> http://www.jtraining.com/blogs/blogger/dhrubo/
>>
>> LinkedIn - http://www.linkedin.com/in/dhrubo
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Dhrubo <dh...@gmail.com>.
No I just poped out the idea since we were considering putting James in OSGi
Anyways if there is not enough time we can for this time stick to just
spring
I am very keen to contribute into this code into Spring. Let me know how I
can be of some use.
On Sat, Dec 26, 2009 at 6:18 PM, Norman Maurer <no...@apache.org> wrote:
> To Be honest, I never used spring-dm but used Spring alot. What is the
> benifit of using spring-dm ? Is it just OSGI?
>
> Thx
> Norman
> 2009/12/26, Dhrubo <dh...@gmail.com>:
> > Hi,
> > Since you are trying Spring ... why not with Spring DM just a
> thought?
> > Thanks ...dhrubo
> >
> > On Sat, Dec 26, 2009 at 3:43 PM, Norman Maurer <
> norman.maurer@googlemail.com
> >> wrote:
> >
> >> Ok because I didn't hear anything against this route I will go ahead
> >> and try to get this stuff done.
> >>
> >> Bye,
> >> Norman
> >>
> >> 2009/12/22 Dhrubo <dh...@gmail.com>:
> >> > Friends,
> >> > Move towards pure Spring away from dead frameworks is highly
> >> > appreciated. I think the move to a OSGi container may come in next
> >> release?
> >> > Thanks ...dhrubo
> >> >
> >> > On Tue, Dec 22, 2009 at 4:22 PM, Norman Maurer <no...@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 ?
> >> >>
> >> >> Bye,
> >> >> Norman
> >> >>
> >> >> Ps: This would eliminate the use of Guice again too
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> >> >> For additional commands, e-mail: server-dev-help@james.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > Thanks ... Dhrubo
> >> > My Book - http://www.apress.com/book/view/1430210095
> >> >
> >> > My Blog -
> >> > http://www.jtraining.com/blogs/blogger/dhrubo/
> >> >
> >> > LinkedIn - http://www.linkedin.com/in/dhrubo
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> >> For additional commands, e-mail: server-dev-help@james.apache.org
> >>
> >>
> >
> >
> > --
> > Thanks ... Dhrubo
> > My Book - http://www.apress.com/book/view/1430210095
> >
> > My Blog -
> > http://www.jtraining.com/blogs/blogger/dhrubo/
> >
> > LinkedIn - http://www.linkedin.com/in/dhrubo
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
--
Thanks ... Dhrubo
My Book - http://www.apress.com/book/view/1430210095
My Blog -
http://www.jtraining.com/blogs/blogger/dhrubo/
LinkedIn - http://www.linkedin.com/in/dhrubo
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Norman Maurer <no...@apache.org>.
To Be honest, I never used spring-dm but used Spring alot. What is the
benifit of using spring-dm ? Is it just OSGI?
Thx
Norman
2009/12/26, Dhrubo <dh...@gmail.com>:
> Hi,
> Since you are trying Spring ... why not with Spring DM just a thought?
> Thanks ...dhrubo
>
> On Sat, Dec 26, 2009 at 3:43 PM, Norman Maurer <norman.maurer@googlemail.com
>> wrote:
>
>> Ok because I didn't hear anything against this route I will go ahead
>> and try to get this stuff done.
>>
>> Bye,
>> Norman
>>
>> 2009/12/22 Dhrubo <dh...@gmail.com>:
>> > Friends,
>> > Move towards pure Spring away from dead frameworks is highly
>> > appreciated. I think the move to a OSGi container may come in next
>> release?
>> > Thanks ...dhrubo
>> >
>> > On Tue, Dec 22, 2009 at 4:22 PM, Norman Maurer <no...@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 ?
>> >>
>> >> Bye,
>> >> Norman
>> >>
>> >> Ps: This would eliminate the use of Guice again too
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> >> For additional commands, e-mail: server-dev-help@james.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Thanks ... Dhrubo
>> > My Book - http://www.apress.com/book/view/1430210095
>> >
>> > My Blog -
>> > http://www.jtraining.com/blogs/blogger/dhrubo/
>> >
>> > LinkedIn - http://www.linkedin.com/in/dhrubo
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-dev-help@james.apache.org
>>
>>
>
>
> --
> Thanks ... Dhrubo
> My Book - http://www.apress.com/book/view/1430210095
>
> My Blog -
> http://www.jtraining.com/blogs/blogger/dhrubo/
>
> LinkedIn - http://www.linkedin.com/in/dhrubo
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Dhrubo <dh...@gmail.com>.
Hi,
Since you are trying Spring ... why not with Spring DM just a thought?
Thanks ...dhrubo
On Sat, Dec 26, 2009 at 3:43 PM, Norman Maurer <norman.maurer@googlemail.com
> wrote:
> Ok because I didn't hear anything against this route I will go ahead
> and try to get this stuff done.
>
> Bye,
> Norman
>
> 2009/12/22 Dhrubo <dh...@gmail.com>:
> > Friends,
> > Move towards pure Spring away from dead frameworks is highly
> > appreciated. I think the move to a OSGi container may come in next
> release?
> > Thanks ...dhrubo
> >
> > On Tue, Dec 22, 2009 at 4:22 PM, Norman Maurer <no...@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 ?
> >>
> >> Bye,
> >> Norman
> >>
> >> Ps: This would eliminate the use of Guice again too
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> >> For additional commands, e-mail: server-dev-help@james.apache.org
> >>
> >>
> >
> >
> > --
> > Thanks ... Dhrubo
> > My Book - http://www.apress.com/book/view/1430210095
> >
> > My Blog -
> > http://www.jtraining.com/blogs/blogger/dhrubo/
> >
> > LinkedIn - http://www.linkedin.com/in/dhrubo
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
--
Thanks ... Dhrubo
My Book - http://www.apress.com/book/view/1430210095
My Blog -
http://www.jtraining.com/blogs/blogger/dhrubo/
LinkedIn - http://www.linkedin.com/in/dhrubo
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Norman Maurer <no...@googlemail.com>.
Ok because I didn't hear anything against this route I will go ahead
and try to get this stuff done.
Bye,
Norman
2009/12/22 Dhrubo <dh...@gmail.com>:
> Friends,
> Move towards pure Spring away from dead frameworks is highly
> appreciated. I think the move to a OSGi container may come in next release?
> Thanks ...dhrubo
>
> On Tue, Dec 22, 2009 at 4:22 PM, Norman Maurer <no...@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 ?
>>
>> Bye,
>> Norman
>>
>> Ps: This would eliminate the use of Guice again too
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-dev-help@james.apache.org
>>
>>
>
>
> --
> Thanks ... Dhrubo
> My Book - http://www.apress.com/book/view/1430210095
>
> My Blog -
> http://www.jtraining.com/blogs/blogger/dhrubo/
>
> LinkedIn - http://www.linkedin.com/in/dhrubo
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Dhrubo <dh...@gmail.com>.
Friends,
Move towards pure Spring away from dead frameworks is highly
appreciated. I think the move to a OSGi container may come in next release?
Thanks ...dhrubo
On Tue, Dec 22, 2009 at 4:22 PM, Norman Maurer <no...@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 ?
>
> Bye,
> Norman
>
> Ps: This would eliminate the use of Guice again too
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
--
Thanks ... Dhrubo
My Book - http://www.apress.com/book/view/1430210095
My Blog -
http://www.jtraining.com/blogs/blogger/dhrubo/
LinkedIn - http://www.linkedin.com/in/dhrubo
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Norman Maurer <no...@googlemail.com>.
Hi Eric,
I don't expect the pure-spring deployment to take more memory then the
phoenix deployment do when its complete. So stay tuned...
Bye,
Norman
2009/12/26 Eric MacAdie <er...@macadie.net>:
> I do not mean to rain on anyone's parade, but I do have one concern. I am
> running James on a VPS host with about 256 MB of memory, and right now James
> uses about 50 MB or so. I noticed from
> http://people.apache.org/builds/james/nightly/bin/ that the Spring version
> is twice as big as the Phoenix/Avalon version. I do not have a lot of memory
> to spare on my VPS account, and I would prefer not to upgrade (I am looking
> for a job and money is tight).
>
> If James with Spring slows stuff down, I may have to look for something else
> to handle email. Maybe I am making a big deal out of nothing, but a cursory
> glance makes it appear that size may be an issue. Other than that: +1
>
> Regards,
> Eric MacAdie
> Pronounced: muh-KAY-dee
>
> Norman Maurer 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 ?
>>
>> Bye,
>> Norman
>>
>> Ps: This would eliminate the use of Guice again too
>>
>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Sat, Dec 26, 2009 at 8:24 PM, Bernd Fondermann <bf...@brainlounge.de> wrote:
> Eric MacAdie wrote:
>> I do not mean to rain on anyone's parade, but I do have one concern. I
>> am running James on a VPS host with about 256 MB of memory, and right
>> now James uses about 50 MB or so. I noticed from
>> http://people.apache.org/builds/james/nightly/bin/ that the Spring
>> version is twice as big as the Phoenix/Avalon version. I do not have a
>> lot of memory to spare on my VPS account, and I would prefer not to
>> upgrade (I am looking for a job and money is tight).
>>
>> If James with Spring slows stuff down, I may have to look for something
>> else to handle email. Maybe I am making a big deal out of nothing, but a
>> cursory glance makes it appear that size may be an issue. Other than
>> that: +1
>
> You are touching 3 different topics here:
> - runtime speed
> - RAM footprint
> - disk footprint
>
> Spring adds significantly to the disk footprint, but not neccessarily to
> the RAM footprint. In fact, only some core stuff of Spring is used.
> Recent releases of Spring provide more fine grained modules, so the disk
> footprint probably could be reduced quite a bit.
>
> I'd expect runtime speed to be exactly the same, because both containers
> only boot the components and step aside after bootstrapping.
the james 3.x is a much bigger beast than 2.x memory wise but spring
has very little to do with it
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Bernd Fondermann <bf...@brainlounge.de>.
Eric MacAdie wrote:
> I do not mean to rain on anyone's parade, but I do have one concern. I
> am running James on a VPS host with about 256 MB of memory, and right
> now James uses about 50 MB or so. I noticed from
> http://people.apache.org/builds/james/nightly/bin/ that the Spring
> version is twice as big as the Phoenix/Avalon version. I do not have a
> lot of memory to spare on my VPS account, and I would prefer not to
> upgrade (I am looking for a job and money is tight).
>
> If James with Spring slows stuff down, I may have to look for something
> else to handle email. Maybe I am making a big deal out of nothing, but a
> cursory glance makes it appear that size may be an issue. Other than
> that: +1
You are touching 3 different topics here:
- runtime speed
- RAM footprint
- disk footprint
Spring adds significantly to the disk footprint, but not neccessarily to
the RAM footprint. In fact, only some core stuff of Spring is used.
Recent releases of Spring provide more fine grained modules, so the disk
footprint probably could be reduced quite a bit.
I'd expect runtime speed to be exactly the same, because both containers
only boot the components and step aside after bootstrapping.
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Dhrubo <dh...@gmail.com>.
Nice point Eric.
I will try to carry out a test and let you know.
Till that time you continue with the older stable version.
On Sat, Dec 26, 2009 at 9:13 PM, Eric MacAdie <er...@macadie.net> wrote:
> I do not mean to rain on anyone's parade, but I do have one concern. I am
> running James on a VPS host with about 256 MB of memory, and right now James
> uses about 50 MB or so. I noticed from
> http://people.apache.org/builds/james/nightly/bin/ that the Spring version
> is twice as big as the Phoenix/Avalon version. I do not have a lot of memory
> to spare on my VPS account, and I would prefer not to upgrade (I am looking
> for a job and money is tight).
>
> If James with Spring slows stuff down, I may have to look for something
> else to handle email. Maybe I am making a big deal out of nothing, but a
> cursory glance makes it appear that size may be an issue. Other than that:
> +1
>
> Regards,
> Eric MacAdie
> Pronounced: muh-KAY-dee
>
> Norman Maurer 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 ?
>>
>> Bye,
>> Norman
>>
>> Ps: This would eliminate the use of Guice again too
>>
>>
>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
--
Thanks ... Dhrubo
My Book - http://www.apress.com/book/view/1430210095
My Blog -
http://www.jtraining.com/blogs/blogger/dhrubo/
LinkedIn - http://www.linkedin.com/in/dhrubo
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Sat, Dec 26, 2009 at 3:43 PM, Eric MacAdie <er...@macadie.net> wrote:
> I do not mean to rain on anyone's parade, but I do have one concern. I am
> running James on a VPS host with about 256 MB of memory, and right now James
> uses about 50 MB or so. I noticed from
> http://people.apache.org/builds/james/nightly/bin/ that the Spring version
> is twice as big as the Phoenix/Avalon version. I do not have a lot of memory
> to spare on my VPS account, and I would prefer not to upgrade (I am looking
> for a job and money is tight).
>
> If James with Spring slows stuff down, I may have to look for something else
> to handle email. Maybe I am making a big deal out of nothing, but a cursory
> glance makes it appear that size may be an issue.
the james 2.x branch is mature, fast and small. james 3.x has a lot
more function but the space cost is high. the only reason why 2.x has
been neglected is lack of developers willing to maintain it. if there
are people who care about a small version of james then there's no
reason why those features that will run small can't be backported.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Remove phoenix-deployment in favor of use pure Spring based
deployment
Posted by Eric MacAdie <er...@MacAdie.net>.
I do not mean to rain on anyone's parade, but I do have one concern. I
am running James on a VPS host with about 256 MB of memory, and right
now James uses about 50 MB or so. I noticed from
http://people.apache.org/builds/james/nightly/bin/ that the Spring
version is twice as big as the Phoenix/Avalon version. I do not have a
lot of memory to spare on my VPS account, and I would prefer not to
upgrade (I am looking for a job and money is tight).
If James with Spring slows stuff down, I may have to look for something
else to handle email. Maybe I am making a big deal out of nothing, but a
cursory glance makes it appear that size may be an issue. Other than
that: +1
Regards,
Eric MacAdie
Pronounced: muh-KAY-dee
Norman Maurer 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 ?
>
> Bye,
> Norman
>
> Ps: This would eliminate the use of Guice again too
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org