You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "David Bosschaert (JIRA)" <ji...@apache.org> on 2018/05/24 15:19:00 UTC
[jira] [Closed] (ARIES-938) Proposal: SPI Catch (plug-in discovery
for both plain Java >=5 and OSGi)
[ https://issues.apache.org/jira/browse/ARIES-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Bosschaert closed ARIES-938.
----------------------------------
Resolution: Won't Do
> 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
> Priority: Major
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)