aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Bosschaert (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-938) Proposal: SPI Catch (plug-in discovery for both plain Java >=5 and OSGi)
Date Wed, 10 Oct 2012 09:57:03 GMT

    [ https://issues.apache.org/jira/browse/ARIES-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473134#comment-13473134
] 

David Bosschaert commented on ARIES-938:
----------------------------------------

I reviewed the code during the email exchange about this topic, see here: http://markmail.org/message/lpia2uacxe72vku2
and support this submission as I find this an interesting way to 'ease your way into OSGi',
by using services that work both inside OSGi and out.

The approach is different from PojoSR (http://code.google.com/p/pojosr)/OSGi Connect (http://www.osgi.org/bugzilla/show_bug.cgi?id=145)
in that rather than introducing the OSGi Service Registry APIs early, it actually does not
introduce the OSGi APIs at all which some people may find a more attractive way to work.
                
> Proposal: SPI Catch (plug-in discovery for both plain Java >=5 and OSGi)
> ------------------------------------------------------------------------
>
>                 Key: ARIES-938
>                 URL: https://issues.apache.org/jira/browse/ARIES-938
>             Project: Aries
>          Issue Type: New Feature
>            Reporter: Jeremias Maerki
>         Attachments: spi-catch.zip
>
>
> As discussed in http://aries.markmail.org/thread/i2vgjryf5caitqmy I propose a new component
for Apache Aries, code-named "SPI Catch", as a complement to SPI Fly.
> SPI Catch provides an abstraction to plug-in discovery that for libraries that make use
of the JAR service provider mechanism (through META-INF/services) to discover plug-ins. It
shields the client from OSGi specifics but all the same offering the dynamics provided through
the OSGi service registry. It is an deal counter-part to Apache Aries SPI Fly which is used
to publish SPI providers as OSGi services. And finally, another focus is on preserving the
runnability totally outside of OSGi.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message