On 5/14/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
While at JavaOne, we 've discussed using OSGI inside ServiceMix.
FWIW this was inspired also from the JBI EG meeting.
There are two areas where it can be used:
* the first one is to replace classworlds / xbean to configure the
container.
Using OSGI will enable better classloader control and will allow updates
of JNDI, container and additionnal services at runtime
* the second area would be to use it for deployement too. This would also
give better control on the classloader (share libraries between SU for
example),
better versionning. But I'm not sure yet how this could be compatible
with
ServiceMix yet. I guess we can use the same mechanism we use in the
Geronimo deployer: the components / SAs are deployed as OSGI bundles
and we use an OSGI listener to dynamically add it to ServiceMix.
Sounds good to me.
Also ServiceMix could itself be an OSGi bundle that can then be
deployed in any OSGi container.
I guess the next step is to use OSGI to deploy an artifact to a cluster
of ServiceMix instances, but i've no idea yet how it can be handled.
I will try to look at the container side first and will send an update soon
(I guess i will create a new branch to experiment a bit).
Any thoughts or additionnal ideas ?
Sounds good to me so far :) Go Guillaume!
Its also probably worth using the Felix maven plugin to turn most of
our jars we have into OSGi bundles too.
--
James
-------
http://macstrac.blogspot.com/
