-
-
16. Re: OSGi integration
"alesj" wrote:
Ok, I'll first try to finish my current idea / impl, with delegation to existing OSGi framework.
Ales can I see this working?
As per this plan the osgi deployer should be able to deploy the osgi bundles in the existing osgi container from other vendor.
I have downloaded the code from here
https://anonsvn.jboss.org/repos/jbossas/projects/jboss-osgi
Right now I see that the osgi bundles are being deployed by the Osgi Deployer in the MC, the osgi services are basically injected as the MC beans in the Microcontainer.
I don't see the osgi classloading implementation yet. -
17. Re: OSGi integration
"vickyk" wrote:
Ales can I see this working?
As per this plan the osgi deployer should be able to deploy the osgi bundles in the existing osgi container from other vendor.
I have downloaded the code from here
https://anonsvn.jboss.org/repos/jbossas/projects/jboss-osgi
This is in some other old repo place.
I never really completed this plan.
But could be an interesting task to do after we're done with our current stuff - building framework from scratch.
Or better, as a facade on top of MC. ;-)"vickyk" wrote:
I don't see the osgi classloading implementation yet.
The jboss-cl project is able to do OSGi kind of classloading.
All you need to provide is the right CLMetaData.
But to make sure this is _really_ the case,
we need to engage the OSGi specific tests on top of jboss-cl. -
18. Re: OSGi integration
"alesj" wrote:
Or better, as a facade on top of MC. ;-)
Yes this looks interesting, is it not what spring app server is doing?
I was thinking of a osgi framework which will have all the jee services plugged in as osgi services i.e We can have these jee services(jta,jca,ejb container ....) plugged in the osgi as bundles and get the full blown jee platform ready ;) -
19. Re: OSGi integration
"alesj" wrote:
The jboss-cl project is able to do OSGi kind of classloading.
All you need to provide is the right CLMetaData.
But to make sure this is _really_ the case,
we need to engage the OSGi specific tests on top of jboss-cl.
Okay here seems the osgi classloading project
http://anonsvn.jboss.org/repos/jbossas/projects/jboss-cl
So when the osgi bundles would be deployed in the Jboss the Jboss Deployment architecture will not create the UCL but the osgi style CL for these deployment artifacts(bundles). -
20. Re: OSGi integration
"vickyk" wrote:
So when the osgi bundles would be deployed in the Jboss the Jboss Deployment architecture will not create the UCL but the osgi style CL for these deployment artifacts(bundles).
I already does that. ;-)
It's just that currently it's import all / export all.
Unless you have jboss-classloading.xml present,
with more exact requirements / capabilities.
As you can see, I already wrote deployers
that do the following transformations:
manifest.mf (A) --> osgi metadata (B) --> cl metadata (C)
Every step of this transformations needs further testing.
(A) --> (B):
- is javacc parsing of manifest.mf bullet proof
- is osgi metadata feature complete
(B) --> (C):
- do we port all of osgi features to cl metadata
- check osgi/cl corner cases
...
I've used some of this stuff already here (for C1 demo):
- http://anonsvn.jboss.org/repos/jbossas/projects/demos/microcontainer/trunk/osgi/boot/bootstrap-beans.xml -
21. Re: OSGi integration
"vickyk" wrote:
"alesj" wrote:
The jboss-cl project is able to do OSGi kind of classloading.
All you need to provide is the right CLMetaData.
But to make sure this is _really_ the case,
we need to engage the OSGi specific tests on top of jboss-cl.
Okay here seems the osgi classloading project
http://anonsvn.jboss.org/repos/jbossas/projects/jboss-cl
So when the osgi bundles would be deployed in the Jboss the Jboss Deployment architecture will not create the UCL but the osgi style CL for these deployment artifacts(bundles).
It doesn't care what the classloader implemention is.
It just creates a ClassLoadingMetaData
http://anonsvn.jboss.org/repos/jbossas/projects/jboss-cl/trunk/classloading/src/main/java/org/jboss/classloading/spi/metadata/ClassLoadingMetaData.java
and populate it with OSGi requirements/capabilities from the manifest
http://anonsvn.jboss.org/repos/jbossas/projects/jboss-cl/trunk/classloading/src/main/java/org/jboss/classloading/spi/metadata/ClassLoadingMetaDataFactory.java
Obviously the old UCL can't implement this feature, but any classloader
that does (e.g. the new VFS ClassLoader) can be used.
This is discussed in more detail in the POJO Microcontainer developers forum.
