[jira] Resolved: (WINK-181) Autoregistration of external providers

["Michael Elman (JIRA)" <ji...@apache.org>]

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

Michael Elman resolved WINK-181.
--------------------------------

    Resolution: Fixed

I've implemented it.
Wink will automatically search for all files called "META-INF/wink-application" in the classpath.
The files found will be loaded using the ApplicationFileLoader using the usual rules.

This process will be on by default, but it can be switched off by setting wink.loadApplications property to false.

> Autoregistration of external providers
> --------------------------------------
>
>                 Key: WINK-181
>                 URL: https://issues.apache.org/jira/browse/WINK-181
>             Project: Wink
>          Issue Type: New Feature
>          Components: Common, Server
>    Affects Versions: 0.1
>            Reporter: Michael Elman
>            Assignee: Michael Elman
>            Priority: Minor
>             Fix For: 0.2
>
>
> Currently we have two files containing providers we have in wink: 
> * META-INF/core/wink-providers - for core providers
> * META-INF/server/wink-providers - for server providers
> Currently there is an assumption that only one of above files exists and it will be loaded.
> I think this assumption is ok, but I think we can provide additional feature of auto-registration of providers located in META-INF/wink-providers file.
> So it should be enough to place wink-jettison-provider.jar in the classpath in order to load the jettison providers.
> We'll also need property that will turn the auto-registration mode on/off, so the user can have a control over the providers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.