DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38385>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38385 ------- Additional Comments From [EMAIL PROTECTED] 2006-01-26 12:00 ------- (In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > ... > > > > Do you mean the remove the deprecated constructors etc or the whole URI class > > implementation ? I was using this constructor because I was not able to obtain > > an uri whose isOpaquePart returned true using the URI(String, boolean) > > constructor, for example from <mailto:[EMAIL PROTECTED]> What I get is an absolute > > uri with relative path [EMAIL PROTECTED] ?? I am asking because I am doing > > some > > testing following RFC3986 and using httpclient.URI class and JDK1.4 > > java.net.URI. > Michele, > I meant the whole class (URI). This is my personal opinion that the URI class > heeds to go, and not that of the HttpClient committers. This issue will be > subject to open discussion on the dev list and eventually to a formal vote. I > will be pressing for deprecation (removal) of this class in favor of JDK14 URI > class, unless someone will step in to maintain and seriously refactor the URI > and related classes. The person who originally wrote the code left the project > about two years ago. The code has been effectively unmaintained ever since. > Oleg Oleg, I am doing these tests with junit on one side and rfc 3986 in the other and I found that java4.net.URI has also some problems. An other thing is that if you have a problem with java.net.URI is not possible to change the code. I would leave at least a wrapper around so that someone can still intervene in case of problems. An other difference is that java.net.URI is unmodificable, while httpclient.URI is modificable, do you think is really needed for it to be modificable ? The code is perhaps in some parts "ugly" but I cannot say too bad things on it since I was using it since when I found it in package org.apache.util that was included in Slide in 2001/2 and also thanks to it and even thanks to its errors I started to become interested in the concept. Its uniqueness is in being quite forgiving in parsing My aim is to make a java4-independent URI only package (may be some URI comparators for different scopes [like network]). I already fit java4 URI into this framework and passed almost all but 3 of the (188) tests, now I am trying with httpclient.URI and I am around 20 failures. I must say that I found a little bit heavy the fact of needing httpclient, codec and even logging for using a URI class. JUnit made me crazy with the class loaded wrong hierarchy for logging... Last thing...does httpclient need java 1.4 ? Ciao Michele -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
