You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2003/07/26 07:14:03 UTC

DO NOT REPLY [Bug 20368] - [JAXP]: Conversion of file names to URIs on Netware fails.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20368>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20368

[JAXP]: Conversion of file names to URIs on Netware fails.

mrglavas@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|parse(File f)               |[JAXP]: Conversion of file
                   |                            |names to URIs on Netware
                   |                            |fails.



------- Additional Comments From mrglavas@apache.org  2003-07-26 05:14 -------
Hi Jean-Pascal,

Without any context, it would be difficult for any of the developers to know 
what your code does. Usually in this community when someone suggests a fix it's 
submitted as a patch: a context diff between your local modified source and the 
source code in CVS. Your suggested fix will be easier to review if you submit 
it as a patch.

I must admit I have no experience with NetWare. What are you suggesting an 
appropriate URI would be for your file 'INTRANET:\security.xml'?

A class such as FilePathToURI will undoubtedly have portability issues, since 
it's unrealistic to cover the cases for every platform in the world. Something 
like this should be part of the JDK's internal API, with different behaviour 
for each platform on which Java's supported. In fact in JDK 1.4, there's a 
method in java.io.File which will convert a File to a system dependent URI. 
Unfortunately we cannot use it, since it didn't exist in lower JDK versions. If 
you're using 1.4 or higher you could try using it as workaround.

By the way, I've changed the bug's summary to something more descriptive.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org