DraK's Klog

That's an awesome news, Spring Integration will provide a Spring based programming and runtime model for EAI patterns.

The configuration will be XML and annotations driven, bringing annotation driven configuration ease of use to EAI !

This article explains how to share a single instance of a spring context between several web applications.

Very usefull.

At last ! Thanx Spring guys This has been at the top of my feature request list for a long time ...

Spring 2.1 will be a killer framework and Spring-OSGi/Spring MVC/JPA the next killer combo !!

This project fills a huge gap, batch processing is amongst those things you never want to do in a project but, that you always get (are forced) to do anyway.

I've developed custom solutions for this matter for almost each project I've been involved with (Spring based of course ).

What I've been looking for for a while

Highligts the Spring JCR integration support. The article uses Jackrabbit as a JCR implementation.

The goal is to release Spring-OSGi 1.0 alongside Spring 2.1 (they'll go out together). Given that the project hasn't actually put out *any* official release yet (milestone or otherwise) at least one milestone build before then will be forthcoming.

The roadmap is looking to be something like this:

• M1 - mid-end March 2007
• M2 - April 2007
• RC1 - May 2007
• other RCs as neeed
• 1.0 final - June 2007

The highly promising but somewhat dangerous domain dependency injection made possible by Spring 2's @Configurable annotation used together with AspectJ seems to have some serious problems.

It has caught the attention of Debasish Gosh who explains what the pitfalls are.

In the wrong hands, that new feature can be devastative, the pitfalls mentionned could lead to some serious problems, it is therefore surprising that Spring 2's rather serious team let that bomb in the wild in such a broken stage.

Pretty hairy but deserves attention ...

Very interesting article by Peter Kriens of the OSGi Alliance. He explains cardinality, optionality and dynamic/static concepts in a dynamic platform such as OSGi.

He explains how the Declarative Services handled those issues and why he thinks the Spring OSGi initiative should follow the same rules.

He also mention that Spring OSGi is a candidate for Declarative Services replacement to be included in OSGi R5 spec.

This would be just amazing. I am a big Spring addict but the thing I like about Spring is IoC, and Spring is not the only IoC container around. I'm not very enthousiast about the idea of the OSGi R5 depending on Spring actually. I hope that the IoC implementation will be pluggable.

Finally, he feels like proxying (as pushed by the Spring OSGi working group) is not such a great idea and I don't feel that way, I hope that work in that direction with continue until either it works or we're very sure it's not possible. At least, it should be possible to be able to choose to work either with proxies or directly with service references.