RFR: JDK-8022748 (new URI(u.toString()).equals(u), does not hold with paths containing colons

2015-12-09 Thread Sebastian Sickelmann
art an discussion/review-process some time ago, see >> second-try below. >> >> Is there someone who wants to discuss/review this change? >> >> Else, should i link my result as reference into the JBS? >> >> -- >> Sebastian >> >> On 10/27/2015

Re: RFR: JDK-8022748 (new URI(u.toString()).equals(u), does not hold with paths containing colons

2015-11-07 Thread Sebastian Sickelmann
time ago, see > second-try below. > > Is there someone who wants to discuss/review this change? > > Else, should i link my result as reference into the JBS? > > -- > Sebastian > > On 10/27/2015 05:24 AM, Sebastian Sickelmann wrote: >> Hi, >> >> i inv

Re: RFR: JDK-8022748 (new URI(u.toString()).equals(u), does not hold with paths containing colons

2015-11-05 Thread Sebastian Sickelmann
estigated the problem described in JDK-8022748[1] i found that > the parser needed to be rescued for confusion while handling relative URIs. > > A URI created through the relativize-method is schemaless and so it > need to handle the special-case (a colon in the path-element). While &g

RFR: JDK-8022748 (new URI(u.toString()).equals(u), does not hold with paths containing colons

2015-10-27 Thread Sebastian Sickelmann
Hi, i investigated the problem described in JDK-8022748[1] i found that the parser needed to be rescued for confusion while handling relative URIs. A URI created through the relativize-method is schemaless and so it need to handle the special-case (a colon in the path-element). While there is

RFR: JDK-8022748 (new URI(u.toString()).equals(u), does not hold with paths containing colons

2015-10-16 Thread Sebastian Sickelmann
Hi, is there someone who wants to sponsor/review my suggested change? -- Sebastian On 10/06/2015 01:13 PM, Sebastian Sickelmann wrote: > Hi, > > i investigated the problem described in JDK-8022748[1] i found that > the parser needed to be rescued for confusion while handling r

RFR: JDK-8022748 (new URI(u.toString()).equals(u), does not hold with paths containing colons

2015-10-06 Thread Sebastian Sickelmann
Hi, i investigated the problem described in JDK-8022748[1] i found that the parser needed to be rescued for confusion while handling relative URIs. A URI created through the relativize-method is schemaless and so it need to handle the special-case (a colon in the path-element). While there is

RFR: JDK-8022748 (new URI(u.toString()).equals(u), does not hold with paths containing colons

2015-09-16 Thread Sebastian Sickelmann
Hi, is there someone how wants to support me by making a patch for JDK-8022748[1] be available for review on cr.openjdk.net? I placed my webrev here: https://dl.dropboxusercontent.com/u/43692695/oss-patches/openjdk/JDK-8022748_0/webrev.zip Thanks Sebastian Am 10.09.2015 um 07:41 schrieb

RFR: JDK-8022748 (new URI(u.toString()).equals(u),does not hold with paths containing colons

2015-09-09 Thread Sebastian Sickelmann
Hi, i investigated the problem described in JDK-8022748[1] i found that we need to rescue the parser for confusion while parsing relative URIs. A URI created through the relativize-method is schemaless and so it need to handle the special-case (a colon in the path-element). While there is another

Re: JDK-8022748

2015-09-07 Thread Sebastian Sickelmann
ian Am 07.09.2015 um 16:30 schrieb Sebastian Sickelmann: > Hi, > > i want to have a closer look to JDK-8022748[1]. > > I make experimented a little and for me it seemed that the relativize > method is making the trouble. > Has someone had a look at it, already? Or is it a academic

JDK-8022748

2015-09-07 Thread Sebastian Sickelmann
Hi, i want to have a closer look to JDK-8022748[1]. I make experimented a little and for me it seemed that the relativize method is making the trouble. Has someone had a look at it, already? Or is it a academic (relativize on "." ) case that is described in the bug-report? Elsewi