Hi Bernd! Am Freitag, den 27.10.2006, 13:09 +0200 schrieb Bernd Fondermann:
> 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. :-) Amazing! Great! :-) > I expect minor problems to arise and JMX is not yet available, but anyway. This will bring us much more insight than 10 hours of discussing. ;-) And it sounds like it could get to something useful soon. > I would like to check this stuff into a sandbox. Yeah, please go on! > This opens some amazing possibilities: > + 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. > + Deploy in J2EE servers and webcontainers etc., whatever a user may > think of This has often been requested. It might not only easier to setup than running two jvms but also opens many possibilities integrating e.g. Mailets with available business logic. > + Use within an OSGi container, as soon as Spring does provide adapters > for this Spring is my favorite for OSGi integration, too. There seem to be big efforts for Spring-OSGi and I guess it is pushed by well-known companies. I expect the current implementation is already usable, at least for doing some experiments. As we have James running with Spring now, I expect a running James inside OSGi soon. Of course at first only a kind of pseudo OSGi-enabled without utilizing most OSGi possibilities. But I'm sure it will bring us again more insight than 10 hours of discussion. + Spring with iBatis as a backend for MailboxManager. :-) I really love the possibilities of AOSD. At the moment, transaction handling and Exception translation is a pain with Torque... But that are dreams of the future. :-) > 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? 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. Joachim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
