I still think that if you are going to go to the work of making james
run well under osgi then it is worth the small additional work of
using blueprint instead of spring-dm so as to not be tied to a
proprietary api. I got activemq running under xbean-blueprint and it
basically consisted of removing some unneeded use of obsolete spring
lifecycle interfaces from a few classes and making sure the spring-
isms needed for startup in spring were in a few classes not needed in
blueprint. Translating a plan from spring to blueprint is pretty
easy, there are basically just a few element name changes.
I think xbean-blueprint is great but I know not everyone agrees and it
is certainly experimental at this point.
thanks
david jencks
On Feb 27, 2010, at 10:33 AM, Norman Maurer wrote:
Hi David,
we are talkin about spring-dm (the modules) not the spring-dm-server.
I just think using spring-dm is the easiest way cause we already use
spring for DI.
Bye,
Norman
2010/2/27 David Jencks <david_jen...@yahoo.com>:
I'd suggest using blueprint rather than spring-dm as it is a
standard.
If you want to poke into experimental territory you could try
xbean-blueprint which, although it currently only works with aries'
blueprint implementation lets you use a schema adapted to the beans
for
configuration.
thanks
david jencks
On Feb 27, 2010, at 9:21 AM, Martin Reisenhofer wrote:
Dear Norman,
Thanks for the answer, i have cycles to integrate james with
spring-dm,
after i finished i publish the sources.
Best Regards
Martin
Norman Maurer wrote:
Hi Martin,
we using spring as container in current trunk. (development
version).
I would love to see some osgi deployment too (using spring-dm) but
noone had the cycles yet to implement it. Contributions are
welcome of
course :)
Bye,
Norman
2010/2/27 Martin Reisenhofer <mar...@meinstein.at>:
Dear James development Team,
there are plans to makes james based on spring and osgi in future?
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
