On 10/27/06, Joachim Draeger <[EMAIL PROTECTED]> wrote:
> + Deploy with custom code/other beans in a much more easy manner
I guess more people know how to work with spring than with phoenix.
And Spring is much less intrusive. Almost every code can be integrated
without change (even James :-) )
> Another consequence is, that there is no _need_ to walk away from
> Avalon. It would be very easy to provide a Spring-bundled release in
> parallel with the present packages.
I even don't see a blocker for going a step further to OSGi together
with Avalon.
BTW: if everything runs well with Spring, which advantages brings us
staying with phoenix, apart from backward compatibility with custom
code?
+ everyone in the dev team knows Avalon/Phoenix
+ it is proven to run James components in a stable production-ready
manner (we don't know yet which Spring-related and
not-running-in-Phoenix-related problems we will run into. this would
be the first painless migration in my career.
+ we still support Java 1.4, we should continue to support Phoenix
To avoid any indignation: I'm not proposing to remove phoenix and switch
to OSGi/Spring right now. But working prototypes will give us the
possibility to evaluate concrete solutions.
Right. This is just a proof-of-concept.
I came to read the Spring 2.0 and suddenly I couldn't resist... never
thought it would work out so well. And I'd like to see similar
prototypes.
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
