|
Hi folks, after digging into the code of servicemix I would
like to start a discussion about some refactorings to “componentize”
servicemix. A bit of background. We are evaluating servicemix for
use in an enterprise level project. We found the current status of the implementation
already extremely promising! But there are some areas where our requirements are
going behind the current implementation of sm like resolver / repository and
security issues etc. While diving into the resolver code we found some
dependencies to other sm packages so that it wouldn’t be that easy to
just replace the current implementation. An other requirement in our project is that we
provide 99,9% availability which means zero downtime for maintenance. This
leads to the requirement of a “pluggable”, “hot deployment”
architecture of the servicemix implementation itself. James told me that you are contributing to and
tracking the GBean project which should be the kernel for Geronimo and maybe
servicemix too. On top of GBean there could be a “real” service container
like a OSGi compliant container. To start the process of “componentizing”
servicemix we would like to contribute as a first step some refactorings to
resolve the cyclic package dependencies within servicemix. We already have
started that work. We also will start a discussion with the GBean people on how
to integrate OSGi / OSCAR with GBean. WDYT? Andreas -- |
