[Design of OSGi Integration] - Why do we need a Felix integration
by thomas.diesler＠jboss.com
Bill asks:
anonymous wrote : Why do we need Felix?
The reasoning goes like this:
JBossAS wants to leverage core concepts from OSGi, (e.g. jboss services want to provide classloader semantics to partially expose code that can then be consumed by other jboss services). This can either be done via jboss proprietary classloading descriptors or via standard OSGi manifest headers. JBossOSGi is about the latter.
Ultimately, you can deploy standard OSGi bundles as jboss services.
To reach that goal is a parallel effort
#1 Provide an OSGi Framework/Runtime
#2 Migrate jboss services to OSGi bundles
The current idea is that we have an OSGi Facade on top of JBossMC, essentially providing an OSGi Framework based on MC.
OSGi bundles should not have a dependency on a particular OSGi implementation, instead they have a dependency on the OSGi core and maybe compendium and other specs.
Having an Apache Felix integration allows us to migrate, test, document, etc our current services to OSGi while not (yet) having an OSGi Framework implementation that is optimized for our needs (i.e. JBossMC based)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222021#4222021
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222021
15 years, 9 months
Separating of specific product functionality in different bundle(s)
by Miroslav Nachev
Hi,
In the source code I see that the support of specific products like
JBossAS is integrated in the core implementation. In my opinion this
should be separated in different bundle. The OSGi Framework
implementation should be pure OSGi implementation without any product
specific things.
Regards,
?Miro.
15 years, 9 months
Re: News from the JBossOSGi Diary
by Thomas Diesler
> We should take care to write the plugin in a way that the actual OSGi
> container we connect to can be 'swapped'.
That's already a given - have a look at
http://jbossosgi.blogspot.com/2009/03/jbossosgi-service-provider-interfac...
Heiko W.Rupp wrote:
>
> Am 27.03.2009 um 17:04 schrieb Ian Springer:
>> I think it would be great if we could write an RHQ plugin for managing
>> JBoss OSGi. That would allow it to be managed using
>
> *argh* This came just too early, as I wanted to do that in a long cold
> summer night :)
> We should take care to write the plugin in a way that the actual OSGi
> container we connect to can be 'swapped'.
>
> Heiko
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
15 years, 9 months
RFC-139 (JMX Control of OSGi) and JBossOSGi
by Miroslav Nachev
Hi,
>From the documentation I see that there is already JMX. Do you have any
plans all management and control (install/deploy, uninstall/undeploy, start,
stop, etc.) to be compatible with RFC-139 (JMX Control of OSGi) ?
Regards,
Miro.
15 years, 9 months
Re: News from the JBossOSGi Diary
by Thomas Diesler
Merci.
I suspect that this would not be very useful (yet). Every jar that
exists in AS 5.x which is not an OSGi bundle is loaded by the OSGi
System Class Loader. To access classes from these jars you must
explicitly include the package name in the configuration, which is
currently defined as:
<entry>
<key>org.osgi.framework.system.packages</key>
<value>
javax.management,
javax.xml.parsers,
org.jboss.logging,
org.jboss.osgi.service,
org.jboss.osgi.spi.management,
org.osgi.framework; version=1.4,
org.osgi.service.packageadmin; version=1.2,
org.osgi.service.startlevel; version=1.1,
org.xml.sax
</value>
</entry>
Instead I'd propose to compile a list of jars that are the primary
candidates to become OSGi bundles. This essentially means adding the
OSGi Manifest Headers to MANIFEST.MF
Once we have that other projects can define their binary dependencies in
terms of OSGi Imports.
Also please note, that the current JBossOSGi release does not (yet) use
the MC as the underlying OSGi framework, which I believe is a
prerequisite to OSGi enable other jboss services large scale.
Having said that, the current JBossOSGi release will already allow us to
turn core services into bundles (i.e. remoting, cache, logging, etc) and
document and test them. Having the OSGi Manifest Headers in those jars
does not hurt AS 5.x.
Generally, the packages defined by 'org.osgi.framework.system.packages'
should be at a bare minimum.
cheers
-thomas
Dimitris Andreadis wrote:
> Nice!
>
> Shouldn't we include the osgi integration in AS 5.x by default, marked
> as preview? I suppose it's an addition deployer with supporting
> libraries, right?
>
> Cheers
> /Dimitris
>
> Thomas Diesler wrote:
>> Hi Folks,
>>
>> in case you care about OSGi, there is news on the "JBossOSGi Diary"
>>
>> http://jbossosgi.blogspot.com/2009/03/jbossosgi-getting-started.html
>>
>> If you want to try out the upcoming JBossOSGi release, please monitor
>>
>> https://jira.jboss.org/jira/browse/JBOSGI-52
>>
>> this will get resolved when we have the download area setup on SF or
>> some other location.
>>
>> cheers
>> -thomas
>>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
15 years, 9 months
Re: News from the JBossOSGi Diary
by Thomas Diesler
Hi Ian,
thanks for your feedback it's much appreciated.
Please monitor
Write an RHQ plugin for managing JBoss OSGi
https://jira.jboss.org/jira/browse/JBOSGI-55
for progress on this task.
The JBossOSGi story is indeed about integration between the various
JBoss projects.
cheers
-thomas
Ian Springer wrote:
> Thomas-
>
> Looks good.
>
> I think it would be great if we could write an RHQ plugin for managing
> JBoss OSGi. That would allow it to be managed using EmbJopr (i.e. an
> admin console webapp like the Felix one you have today) or Jopr/JON. Not
> only would we be eating our own dog food, but I think we'd end up with
> something a lot nicer than Felix with not a ton of work required. Please
> ping me or one of the other developers on the JON team if you'd like to
> discuss this some more. We'd be glad to help you get started writing a
> plugin.
>
> -Ian
>
> P.S. I noticed a couple typos in the blog:
>
> artefacts
> documentaion
>
> On 3/27/2009 11:01 AM, Thomas Diesler wrote:
>> Hi Folks,
>>
>> in case you care about OSGi, there is news on the "JBossOSGi Diary"
>>
>> http://jbossosgi.blogspot.com/2009/03/jbossosgi-getting-started.html
>>
>> If you want to try out the upcoming JBossOSGi release, please monitor
>>
>> https://jira.jboss.org/jira/browse/JBOSGI-52
>>
>> this will get resolved when we have the download area setup on SF or
>> some other location.
>>
>> cheers
>> -thomas
>>
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
15 years, 9 months
Re: JBossOSGi download area
by Thomas Diesler
Mark Newton wrote:
> Hi there,
>
> Looks like you've been busy :)
yes, with osgi and taking care of my two beautiful girls ;-
>
> Where have you created your project pages for this as it would be best
> to use our new Magnolia CMS with it's redesigned L&F and navigation
> structure?
So far, I use the wiki as the entry point. If Magnolia CMS does provide
me with a professional entry point that is publicly available - that
would be great.
>
> The plan is for all projects to use this as we're putting all of our
> resources behind it for ongoing development and support. If you need a
> login then Ryszard (in cc) can create one for you to use at
> http://jboss.org/author
>
> It doesn't take long to create a great looking site and you can ask for
> help creating a project logo and banner from our Visual Design team
> (James and Cheyenne, also in cc)
>
> If you need a hand then let me know.
>
> thanks,
>
> Mark
>
>
> On 25 Mar 2009, at 13:02, Thomas Diesler wrote:
>
>> Hi Mark/Luc,
>>
>> I'm about to release jboss-osgi and I am looking for an appropriate
>> download area.
>>
>> In the documentation (that I'm still working on) I say
>>
>> "Currently, the JBossOSGi Installer is available from the JBoss Maven
>> Repository. You can download the latest version from
>> jboss-osgi-distribution directory."
>>
>> http://jbmuc.dyndns.org:8280/hudson/job/Container-JDK1.6/ws/jboss-osgi/bu...
>>
>>
>> This would work for now but is unprofessional IMHO and does not give
>> me download statistics either.
>>
>> Any idea how to setup the download more appropriately?
>>
>> cheers
>> -thomas
>>
>> --
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> Thomas Diesler
>> JBoss, a division of Red Hat
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> Mark Newton
> JBoss Community Lead
> Mobile: +41 7657 47730
> Office: +41 41 728 7253
> Skype: callto://newtonmark
> Email: mark.newton(a)jboss.org
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
15 years, 9 months
