On 10/27/06, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
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.

Agreed. I expected it to be a limit on container migration, but it is
not a blocker, just an obstacle ;-)

> 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 ;-)

Probably no. Spring Reference and API doc is extremly good.

Can you elaborate on the "very lean and mean gluecode" ?

1 Main class, 5 classes for injecting Logger and calling
contextualize(), service(), configure(), initialize().
Helpers for Logger, ServiceManager, providing Configuration.

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.

Converting assembly.xml to spring-config.xml is straightforward on the
syntax level, but I had to do some tweaking here and there.

> 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

Sure, no stopping here :-)

> + full control over and possible customization of logging, configuration
> and component lifecycle

Customization of logging and configuration is already available in phoenix.

Yes, sure. But now it becomes easier to control over the whole
application lifecycle.
For example, it would now be relatively easy at startup time to
intercept the configuration loaded from file (base configuration) and
enhance it with other data (e.g. additional domain names, etc.) coming
from another source.

 Bernd

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to