Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353619 - Need HttpClient.setURI(URI) method
Summary: Need HttpClient.setURI(URI) method
Status: CLOSED DUPLICATE of bug 353623
Alias: None
Product: Jetty
Classification: RT
Component: client (show other bugs)
Version: 7.4.5   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: 7.5.x   Edit
Assignee: Joakim Erdfelt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-02 12:58 EDT by Joakim Erdfelt CLA
Modified: 2011-08-29 17:31 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joakim Erdfelt CLA 2011-08-02 12:58:50 EDT 
When working with complex URI's, it is not a good idea to keep translating back and forth between URI and string and back again, especially if we already have a good java.net.URI object and just want the HttpClient to just use it.

Requesting a HttpClient.setURI(URI) method to prevent this needless (and fragile) String <-> URI translation step.
Comment 1 Greg Wilkins CLA 2011-08-25 00:25:21 EDT 
Why does HttpClient need a setURI?    The URI is a property of an HttpExchange not the client.

Happy to avoid converting to/from URI's but don't see the need on this class.
Comment 2 Joakim Erdfelt CLA 2011-08-25 12:13:37 EDT 
You are correct, HttpExchange.setURI(URI) is the best place for that.
Comment 3 Michael Gorovoy CLA 2011-08-29 17:31:30 EDT 

*** This bug has been marked as a duplicate of bug 353623 ***