[
https://issues.apache.org/jira/browse/WINK-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757695#action_12757695
]
Hudson commented on WINK-99:
----------------------------
Integrated in Wink-Trunk-JDK1.5 #166 (See
[http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.5/166/])
Port wink-itest-inheritance to RestClient
See []
Port wink-itest-filter to use RestClient
See []
Port tests to use Wink RestClient
See []
> Use Wink Client instead of Apaceh Http Client in integration tests
> ------------------------------------------------------------------
>
> Key: WINK-99
> URL: https://issues.apache.org/jira/browse/WINK-99
> Project: Wink
> Issue Type: Task
> Components: Testsuite
> Affects Versions: 0.1
> Reporter: Martin Snitkovsky
> Assignee: Bryant Luk
>
> Currently, integration tests are using Apache Commons Http Client. I think we
> should switch to Wink Client instead.
> I everyone agrees with this change, i would prefer that the person that will
> perform this switch is the one that is not familiar with Wink Client API.
> NOTE for issue assignee:
> Wink client has an integration with Apache Http Client
> (wink-client-apache-httpclient module), so some of tests should use Wink
> Client + Apache Client instead of default Wink client that uses
> HttpUrlConnection.
> {code}
> // create the client that uses Apache DefaultHttpClient as underling
> Http client.
> RestClient client = new RestClient(new ApacheHttpClientConfig(new
> DefaultHttpClient()));
>
> // create the resource to make invocations on
> Resource resource =
> client.resource("http://myhost:80/my/service");
>
> // invoke GET on the resource and receive the response entity as a
> string
> String entity = resource.get(String.class);
> {code}
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
