FYI, I've just checked in the stuff I 'm working on at
http://svn.apache.org/repos/asf/incubator/servicemix/branches/osgi/
If you build the project, you should be able to run the server in
./dist/target
by launching
java -jar bin/servicemix.jar
or
./servicemix
There is really not much here, just enough to take a look at OSGI.
On 5/14/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
While at JavaOne, we 've discussed using OSGI inside ServiceMix.
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.
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 ?
--
Cheers,
Guillaume Nodet
------------------------
Principal Engineer, IONA
Blog: http://gnodet.blogspot.com/
--
Cheers,
Guillaume Nodet
------------------------
Principal Engineer, IONA
Blog: http://gnodet.blogspot.com/
