Bernd Fondermann wrote:
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. :-)
Cool!
Well, I expected it wasn't hard to move away from Phenix. The hard part
would be remove the avalon framework, but as I always said I think
avalon framework is good and still not a big limit for James.
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 admit I would have expected more than 10 working hours. I'm sure
you're better than me at Spring ;-)
Can you elaborate on the "very lean and mean gluecode" ?
I think we could create a script to automatically generate the spring
bean configuration starting from assembly.xml but I'd like to know if
what you described as "gluecode" is dependent from the assembly content
or is generic things to replace phoenix.
I expect minor problems to arise and JMX is not yet available, but anyway.
If you did the rest in 10 hours we can give you 3 more hours for JMX :-P
I would like to check this stuff into a sandbox.
++1
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
++1
+ full control over and possible customization of logging, configuration
and component lifecycle
Customization of logging and configuration is already available in phoenix.
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 agree, this would be good!
And it seems to be not intrusive and as an additional package we could
also put this in next-major (if this will be stable and others will like
this too)
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
