[forge-dev] Forge 2.0 and OSGi

Dan Allen dan.j.allen at gmail.com
Mon Sep 24 20:21:27 EDT 2012


My feelings about this question are likely consistent with what the JBoss
AS team has to say about their OSGi story. The container can be OSGi
compliant, we just don't want to build it on OSGi. In a diagram, that looks
like:

OSGi plugin layer
------------------
    Forge Core
------------------
  JBoss Modules

The general argument here is that OSGi is a fine target for
application-level programmers, but it has too much architectural coupling
for building containers (such as JBoss AS and Forge).

Therefore, I think a reasonable approach is to have an OSGi-compliant
plugin layer so that plugin writers can code against OSGi and be able to
have their plugin loaded as a bundle. This layer would be in addition to
the preferred plugin layer, which loads the plugin as a (JBoss) module.

As for how to create that OSGi-compliant plugin layer, I have no idea.
That's not my dept.

Sound reasonable?

-Dan

On Mon, Sep 24, 2012 at 5:02 PM, <ggastald at redhat.com> wrote:

>  Hello,
>
> I've been done some thinking and researching for Forge 2.0 based on the
> last forge meeting we had and the current code in the 2.0 branch, and it
> seems that the architecture we're looking for is very close to OSGi
> architecture itself (regarding to plugability and modularity).
>
> I'm also afraid that we'll face the same problems that OSGi tries to
> solve. As my current experience with OSGi is next to minimal (and probably
> to better understand why and have some arguments if someone asks me about
> it), I would like some opinions about the advantages/disadvantages of why
> not having the Forge container as an OSGi compliant solution.
>
> Also, don't get me wrong: I am not trying to convince anyone of using OSGi
> into the forge core, just want to understand better why this architecture
> is not a viable solution so far. I know Lincoln is against using it, but I
> just want some arguments in case someone asks me in conferences and stuff :)
>
> Of course, we need to keep using CDI and annotations as well. So if it's
> possible to have that and at the same time the modularity (and plugability)
> offered by OSGi, it would be awesome.
>
> Looking forward for your answers !
>
> Best Regards,
>
> --
> *George Gastaldi* | *Senior Software Engineer*
> JBoss Forge Team
> Red Hat
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>


-- 
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://google.com/profiles/dan.j.allen
http://mojavelinux.com
http://mojavelinux.com/seaminaction
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20120924/509c3959/attachment-0001.html 


More information about the forge-dev mailing list