james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernd Fondermann <bf_...@brainlounge.de>
Subject container and component model [Re: libs in spring deployment [Re: [jira] Commented: (JAMES-834)...]
Date Sun, 01 Mar 2009 19:33:55 GMT
> IMHO phoenix and the avalon framework are holding the server back

Yes, they do. but not everyone here thinks this way, AFAIU. But maybe 
this has changed.

> i would like to be able to run james on the phoenix container but
> don't want the server architecture to be determined by it. my
> preference would be to replace the intrusive Avalon interfaces with
> JSR-250 annotations. this would provide a natural path toward smoother
> integration with JEE containers whilst providing an easy route to
> retain phoenix compatibility. if this sounds like an idea would
> exploring, i'll open a JIRA with more details.

Maybe worth looking into at ACEU09's hackathon. WDYT?
I'll have a look at the JSR250 spec over the next days to be able to 

Choosing an approach like this makes a lot of sense to me. We don't know 
how all this container stuff evolves over the next years - whether it is 
Spring or Pico/Nano or OSGi or Phoenix or whatever.

> in the medium term, i think the best approach for james would be a
> blended micro-kernel approach (like service-mix, for example) with a
> top level service locator layer for coursely grained services (with
> internal structure below that assembled by any supported dependency
> injection mechanism).

Maybe, I'd like to think about planning that space trip later. Phoenix 
still has too much grativation on James. It's hard enough to eventually 
reach a higher orbit to be able too move away and get to the next planet.


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

View raw message