Re: container and component model [Re: libs in spring deployment [Re: [jira] Commented: (JAMES-834)...]

[Robert Burrell Donkin <ro...@gmail.com>]

On Sun, Mar 1, 2009 at 7:33 PM, Bernd Fondermann <bf...@brainlounge.de> 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 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?

+1

i'm very keen to look Mailet 3 as well, especially focussing on
general MIME documents so that micro-messaging and blogging can be
added into the mix and processed by mailets

but i think that annotations are the best approach for both mailets and james

> I'll have a look at the JSR250 spec over the next days to be able to
> comment.

cool - the good news is that it's small :-)

> 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.

+1

>> 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.

:-)

- robert

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