Hi everyone,
I still can't quite believe it but in around 10 working hours I managed
to get James 2.3 up and running - not from Phoenix, but booting using
Spring 2.0. :-)
With thorough tests still pending, it is remarkable that James code and
the configuration remains unchanged. It is just providing new wrappers
for the Avalon lifecycle, throwing all the jars together, converting
assembly.xml to Spring bean configuration and providing some very lean
and mean gluecode.
Never thought it to be so easy.
I expect minor problems to arise and JMX is not yet available, but anyway.
I would like to check this stuff into a sandbox.
This opens some amazing possibilities:
+ Deploy with custom code/other beans in a much more easy manner
+ Deploy in J2EE servers and webcontainers etc., whatever a user may
think of
+ Use within an OSGi container, as soon as Spring does provide adapters
for this
+ full control over and possible customization of logging, configuration
and component lifecycle
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.
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
