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: libs in spring deployment [Re: [jira] Commented: (JAMES-834)...]
Date Sun, 01 Mar 2009 20:09:36 GMT
On Sun, Mar 1, 2009 at 7:21 PM, Bernd Fondermann <bf_jak@brainlounge.de> wrote:
> Robert Burrell Donkin wrote:
>>
>> i think using phoenix blocks to wire the spring version together seems
>> unnatural. i suspect that if we drop support for phoenix block wiring
>> in the spring deployment then these libraries would not be necessary.
>> can anyone see any problems with this approach?
>
> community-wise: maybe. people here had reservations to switch to spring, so
> this way seemed to be an acceptable path for everyone.

i've found that using phoenix is a major limitation as far as
integrating modern components into james is concerned. the way the
wiring works is just so intrusive and clumsy that it starts to dictate
architecture. no one new is going to invest time in learning a dead
container.

> technical: no, it would make the implementation a lot lighter if we were
> using straight Spring.
> matainability-wise: if we kept phoenix and would also support a seperate
> spring-depl, it would be more work, more testing etc. for example you'd need
> to maintain 2 sets of config files.

i'm happy that the smoke tests work well enough for basic operations,
we just need to get hudson to run them

i was just wondering about replacing the assembly wiring at this
stage, with the configuration remaining common

IMHO the cost of creating and maintaining phoenix wiring for the new
components i'm interested in (JCR, JPA, Camel etc) is high. spring or
OSGi wiring is already available for these technologies.

- robert

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


Mime
View raw message