[
https://issues.apache.org/jira/browse/WINK-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755922#action_12755922
]
Eli Baram commented on WINK-181:
--------------------------------
I like the Idea.
I think that since this file is actually a simple application and if resources
are register there they will also be loaded, we should set the name to be
"wink-application" instead of "wink-providers".
This feature can be use also by application providers, in a way that a
developer can pack all the resources and providers in a jar add the
wink-application, and that's it. all left to do in order to register it is to
have the jar in the class path.
If implementing this feature we must also add the registration information to
the log files, in INFO level, to help users understand where the resources and
providers were loaded from to the application.
> 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.
