DraK's Klog

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 !!

Tiny code sample which explains how to bootstrap Equinox in a Java application.

Have you ever wanted to try OSGi, but found setting up the build and working out the manifest too much of a chore?

If so then help is at hand - over the last few months, I have been developing a set of Maven archetypes and plugins to automate much of the manual work required in creating an OSGi project.

The Pax Wicket Service is an OSGi service for supporting the creation of Wicket applications running on the OSGi platform.

The Pax Wicket Service allows you to load and unload Wicket pages and page content in runtime. It also allows you to register new Wicket Applications in runtime. All this without restarting the OSGi container.

This pages describes the EasyBeans over OSGi's architecture and the way to test it from the EasyBeans' sandbox.

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

This code sample highlights how to run Spring-OSGi together with the servlet bridge (or the general HTTP service) in equinox.

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.

Impressive use of OSGi and Jini ...

Newton is a distributed component framework in which the components can be simple POJOs or wrappers around components based on other models.

Newton recognises the dynamic nature of distributed computing and seeks to address the needs of components living in this world. To this end Newton moves code around the network installing it on demand and removing it when it is no longer in use. Newton also dynamically wires up runtime service dependencies between components and rewires them as service provider components come and go.

Newton describes distributed systems using the emerging SCA standard. Newton provides a highly dynamic SCA implementation. It is able to install and manage SCA composites distributed across a large number of JVMs, continually comparing the deployed composite graph to a specified target state and making adjustments in response to failures and network topology changes.

Newton makes use of OSGi for wiring up composites within a single JVM and Jini technology for tracking and wiring up dependencies between composites in different JVMs.

Offers a text based and graphical based UI.