The team really appreciates your comments and your hardwork in writing up this piece.

We’re really happy with the way plans are shaping up, we’d love to hear any comments that you have.

Thanks,

Rob

Maybe I was not clear enough in my article. Indeed, Spring DM Server is fully OSGi compliant (equinox kernel) and therefore, it allows to deploy manually every bundle. My points was not really against Spring DM Server, the lack of a deployment standard on OSGI for multiple bundle distribution is lacking and being tight to any container is something I tend to avoid. Anyway, I heard of plans, I will try this soon. Great project, great product, great work.

I wanted to clear up one point. PAR files are just an option for dm Server. You can still deploy individual bundles directly to the server. PAR files are mainly used when you want to get isolation for your applications. In the 2.0 version we have introduced the notion of plan files that allow the same benefits as PAR files whilst allowing bundles to be packaged separately.

We looked at the start level service for a long time and we didn’t really like the model that it suggests. We prefer to rely on service dependencies to handle module interdependencies rather than strict timing blocks.

Thanks again!

Rob Harrop
Lead Engineer, SpringSource dm Server

The model-driven aspect allows you to describe your components (and wiring of them together) in a document and then automate the deployment and on-going maintainence (self-healing resilience, update, removal, etc) of these within the runtime.

You can find out more and get an evaluation version at http://www.paremus.com.