-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Jeroen, I agree this looks very dissapointing. Still only one of those bugs[0] slightly mentions the implicit "////" to "//" conversion.
For all other problems mentioned problems we decided to share them (e.g. treating the slash after the hostname as part of the URL path although RFC 1738 explicitly states not to do so). cu Robert [0] - http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5014591 Jeroen Frijters wrote: > Robert Schuster wrote: > >>However I consider these tests wrong because they violate the >>URL spec. > > > Some people (like me) believe it is more important, in some cases, to be > compatible with the reference implementation than to the spec. > > >>proto:////p1/p2 >> >>is not the same as >> >>proto://p1/p2 >> >>Furthermore this is exactly the bug which causes trouble in >>our XML parser and since the other implementation contains it >>too I send Sun a problem report. >> >>I am going to fix these tests afterwards. Obviously they will >>then fail on Sun-based VMs until they fix the problem, too. > > > It's highly unlikely Sun will fix their code, see also: > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4737160 > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4110155 > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4447088 > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5014591 > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5018803 > > Regards, > Jeroen > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFDS3x9G9cfwmwwEtoRAvyFAKCAFtDW/sVSkWzPmVMcTzylOhGUDgCfQGPu 6nYsiyaLzpNBNs8bLK9b0HY= =tdWk -----END PGP SIGNATURE----- _______________________________________________ Classpath-patches mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath-patches
