"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/trun...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179723#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...