ModelBus 2.0 Released
22.07.2016 ModelBus is now available in version 2.0! This marks the start of a new generation of the proven model driven tool integration and automation technology platform.
ModelBus is now available in version 2.0! This marks the start of a new generation of the proven model driven tool integration and automation technology platform.
The underlying architecture of the ModelBus was renewed, to gain more flexibility and be able to support new use cases. This version is a major release and contains breaking changes for custom services running on the ModelBus infrastructure. The repository, however, remains backwards compatible with existing clients (including older versions of the Eclipse ModelBus Teamprovider). The new version of the ModelBus Teamprovider stays compatible with old ModelBus repositories as well.
Below we want to show you some of the highlights of the newest ModelBus release.
Support for newest Eclipse versions
We now support Eclipse Luna, Mars and Neon as the basis for the ModelBus server, as well as the clients.
The ModelBus Teamprovider was updated accordingly, the support for Eclipse Papyrus now includes version 2.0.
Support for Eclipse Kepler and older Eclipse releases had to be dropped. The Papyrus specific support (locking elements from within the editor) is limited to version 1.1 or newer. On Mac OS the ModelBus server is available with an Eclipse Mars or Neon base; Luna support had to be retired.
Eclipse Communication Foundation integration
ModelBus 2.0 integrates with the OSGi Remote Services and Remote Service Admin implementation Eclipse Communication Foundation (ECF). ModelBus provides an ECF container supporting JAX-WS services. This framework is way more flexible than the previously used CXF DOSGi. It enables exciting possibilities like pluggable service discovery mechanisms and communication protocols. As a result, integration into new or existing distributed and resilient software architectures and infrastructures can be achieved with less effort.
Better support for standalone services
Previously it was difficult to create a custom ModelBus service running in a standalone application instead of being deployed in the ModelBus server. With the advent of scalable microservice architectures this is a stepping stone towards scalable model driven continuous integration.
The example services that can be created via the Teamprovider wizards were updated to include product definitions that can be used as a starting point to create standalone and isolated services.
More standard compliant
We are now using more official JAX-WS APIs instead of providing a tailored CXF implementation and integration layer. The JAX-WS Endpoint API is used to publish services, which allows switching the underlying JAX-WS implementation. Standard JAX-WS annotations are now used for the ModelBus interaction pattern. This eliminates the need for custom JAX-WS framework specific extensions. With these changes ModelBus 2.0 by default runs on a plain JDK without the need of an additional JAX-WS implementation.