Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Date: Tue, 9 Oct 2012 14:45:02 +0000 (UTC)
From: "Jeremias Maerki (JIRA)" <jira@apache.org>
To: dev@aries.apache.org
Message-ID: <1416899396.14753.1349793902870.JavaMail.jiratomcat@arcas>
In-Reply-To: <1284956715.14736.1349793782959.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (ARIES-938) Proposal: SPI Catch (plug-in discovery
 for both plain Java >=5 and OSGi)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ARIES-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeremias Maerki updated ARIES-938:
----------------------------------

    Attachment: spi-catch.zip

The attached spi-catch.zip is the initial proposal. It has a README.txt with some documentation. There is one issue that I haven't been able to fix, yet: The integration tests run from within Eclipse, but there is an exception running it from the Maven build. If anyone has an idea, this would be most welcome. I'm not so familiar with Maven.
                
> 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