You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2009/09/07 12:59:57 UTC
[jira] Commented: (WINK-164) Client should load common providers
from wink-providers
[ https://issues.apache.org/jira/browse/WINK-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752088#action_12752088 ]
Hudson commented on WINK-164:
-----------------------------
Integrated in Wink-Trunk-JDK1.5 #131 (See [http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.5/131/])
load providers from 'wink-providers' file using the ApplicationFileLoader
See []
> Client should load common providers from wink-providers
> --------------------------------------------------------
>
> Key: WINK-164
> URL: https://issues.apache.org/jira/browse/WINK-164
> Project: Wink
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.1
> Reporter: Michael Elman
> Assignee: Michael Elman
> Fix For: 0.2
>
>
> Currently client loads hard-coded providers (see ClientConfig.initDefaultApplication)
> it should load providers from 'wink-providers' file using the ApplicationFileLoader.
> If "wink-providers" contains providers that can run only on server side, they should be moved to wink-server component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.