You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Michael Elman (JIRA)" <ji...@apache.org> on 2009/09/15 10:41:57 UTC
[jira] Created: (WINK-181) Autoregistration of external providers
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
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.
[jira] Closed: (WINK-181) Autoregistration of external providers
Posted by "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 closed WINK-181.
------------------------------
> 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.
[jira] Resolved: (WINK-181) Autoregistration of external providers
Posted by "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.
[jira] Commented: (WINK-181) Autoregistration of external providers
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755980#action_12755980 ]
Hudson commented on WINK-181:
-----------------------------
Integrated in Wink-Trunk-JDK1.5 #155 (See [http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.5/155/])
automatic registration of wink-application
See []
> 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.
[jira] Assigned: (WINK-181) Autoregistration of external providers
Posted by "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 reassigned WINK-181:
----------------------------------
Assignee: Michael Elman
> 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.
[jira] Commented: (WINK-181) Autoregistration of external providers
Posted by "Eli Baram (JIRA)" <ji...@apache.org>.
[ 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.