[JBoss OSGi] - Re: OSGi and MicroContainer
by alesj
"speleomaniac" wrote : Thx for the quick reply...
|
| Unfortunately, most of my experience with the configuration of ClassLoaders with
|
| * jboss-app.xml for .ear
| * jboss-web.xml for .war
| * jboss.xml for the rest
|
| was catastrophic.....That is one of the reason why OSGi is so attractive to me....
|
| In one of my old projects, we were working with JBoss Portal and we had tried to isolate the classloaders with the mentioned files, that totally killed the portal framework, then after I am always keeping an eye open for the alternatives....
|
Yeah, those files are really meant for basic usage / isolation.
In your case you still needed to do a lot of "communication" with portal engine,
which is far from trivial to properly isolate.
"speleomaniac" wrote :
| I was just looking to see is this scenario possible with JBoss, I would look closely to JBoss OSGi implementation and this discussion about MicroContainer and OSGi had confused me little bit...but thx for the answer...
You can follow our OSGi progress more closely here:
* http://jbossosgi.blogspot.com/
This is the presentation I did at JavaOne this year:
* http://anonsvn.jboss.org/repos/jbossas/projects/presentations/trunk/micro...
it explains a bit where we are, and we're we headed with our CL/OSGi development.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248140#4248140
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248140
17 years
[JBoss OSGi] - Re: OSGi and MicroContainer
by speleomaniac
Thx for the quick reply...
Unfortunately, most of my experience with the configuration of ClassLoaders with
* jboss-app.xml for .ear
* jboss-web.xml for .war
* jboss.xml for the rest
was catastrophic.....That is one of the reason why OSGi is so attractive to me....
In one of my old projects, we were working with JBoss Portal and we had tried to isolate the classloaders with the mentioned files, that totally killed the portal framework, then after I am always keeping an eye open for the alternatives....
Another reason, why OSGi is so attractive, we are using Maven and the
ideas from OSGi fitting really good with developing with Maven (to be able to define during development time exactly what libraries you are going to use and this information transferred to runtime....)
My actual project is an B2B project with Web Services, we are the gateway for several other services and these services releases periods are most of the time are not conform with ours...
When they make version changes, that is causing lots of headaches for us, the feature of OSGi is a perfect solution for us, lets say deploy a bundle, inactivate it and when the time is right activate it....
I was just looking to see is this scenario possible with JBoss, I would look closely to JBoss OSGi implementation and this discussion about MicroContainer and OSGi had confused me little bit...but thx for the answer...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248132#4248132
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248132
17 years
[JBoss OSGi] - Re: OSGi and MicroContainer
by alesj
"speleomaniac" wrote :
| Or I am wrong and this would not occur in JBoss MicroContainer....
|
It all depends on how you would configure your classloading.
e.g. by default - as you might probably know - in JBossAS everything is flat,
meaning everything can see everything, and it's the first-loaded rule on which class gets loaded
While this is pretty nice/useful for most of the time
- I personally liked this very much while I was still a plain user of JBossAS :-) -
but of course it can be a pita sometimes.
But that's why you have classloading isolation.
While in JBossAS itself you have those custom and easy to configure files to apply cl isolation
* jboss-app.xml for .ear
* jboss-web.xml for .war
* jboss.xml for the rest
these can be called legacy with the new Microcontainer as the kernel.
As part of MC, we completely changed our classloading and deployers layer, making it a lot richer.
For classloading, OSGi model was definitely something we looked to support (among other potential new cl models).
You can already do most of the OSGi kind of features, only missing on some corner cases.
The new syntax is currently supported in jboss-classloading.xml files,
while we're already working on making this portable to plain OSGi manifest.mf files.
Unfortunately the docs are not that comprehensive:
* http://www.jboss.org/index.html?module=bb&op=viewtopic&t=159343
but I do try to answer all of the question releated with MC and therefore its new cl layer in our MC user forum:
* http://www.jboss.org/index.html?module=bb&op=viewforum&f=228
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248124#4248124
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248124
17 years