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/17 09:39:57 UTC
[jira] Commented: (WINK-191) ClientConfig's loadWinkApplications
always true
[ https://issues.apache.org/jira/browse/WINK-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756401#action_12756401 ]
Hudson commented on WINK-191:
-----------------------------
Integrated in Wink-Trunk-JDK1.5 #160 (See [http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.5/160/])
fix []
> ClientConfig's loadWinkApplications always true
> -----------------------------------------------
>
> Key: WINK-191
> URL: https://issues.apache.org/jira/browse/WINK-191
> Project: Wink
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.2
> Reporter: Bryant Luk
> Assignee: Michael Elman
> Fix For: 0.2
>
>
> The ClientConfig's loadWinkApplications can be set to false, but I don't see a way to not have it automatically load the Wink applications. initDefaultApplication is called from the ClientConfig constructor so it would always be loaded.
> There are cases where the client may only want to load one or two providers from a JAR or in some special instance, the client for this particular run would not want to load all the providers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.