james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Burrell Donkin <robertburrelldon...@gmail.com>
Subject Re: container and component model [Re: libs in spring deployment [Re: [jira] Commented: (JAMES-834)...]
Date Sun, 01 Mar 2009 20:50:32 GMT
On Sun, Mar 1, 2009 at 8:05 PM, David Jencks <david_jencks@yahoo.com> wrote:
> On Mar 1, 2009, at 11:33 AM, Bernd Fondermann wrote:
>>> 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 found the avalon/pheonix stuff rather hard to understand.  IMO if it's
> kept it would be best as a layer on top of a container-agnostic component
> layer.


>>> 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.
>> +1.
>> 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
>> comment.
> Also note that something very like spring + osgi is coming to the next osgi
> spec as rfc 124 blueprint service.

sounds good

> Also IIUC JavaEE6 is going to have a much more general dependency injection
> framework, from what may be currently the web beans spec proposal.  I don't
> know any details on this.
> Geronimo xbean has a bunch of libraries that make annotation scraping and
> component creation pretty easy -- xbean-finder and xbean-reflect.


> I'd kind of worry that if you start using annotations you are going to be
> building yet another wiring framework which may not be the ideal focus of
> this project.

(unfortunately) i'm not sure a consensus would be possible about
picking a more modern approach

the annotations are the smallest way (i could think of) to remove the
intrusive avalon framework without breaking the phoenix container. i
see them as a stepping stone useful for the phoenix container.

i've outlined the proposal on https://issues.apache.org/jira/browse/JAMES-893

feedback welcomed :-)

- robert

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

View raw message