[WINK-99] Use Wink Client instead of Apaceh Http Client in integration tests

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.1
• Fix Version/s: 1.1
• Component/s: Testsuite
• Assignee: Bryant Luk
• Reporter: Martin Snitkovsky
• Created: 15/Jul/09 07:19
• Updated: 13/Jul/13 20:13
• Resolved: 28/Jan/10 05:32

Description

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.

       // 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);