Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-7800

xml-commons resolver does not handle Windows paths properly

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.1.2
    • Fix Version/s: EAP_EWP 5.2.0 ER4
    • Component/s: Other
    • Labels:
      None
    • Affects:
      Release Notes
    • Release Notes Text:
      Hide
      The Apache xml-commons resolver did not correctly convert paths to URLs, instead it prefixed the path with <literal>file:</literal>, then passed it to the URL constructor. This method was incompatible with Microsoft Windows Server because <literal>file:C:\...</literal> is not a valid file URL. This function has been corrected and the method of converting paths to URLs is now compatible with all supported platforms.
      Show
      The Apache xml-commons resolver did not correctly convert paths to URLs, instead it prefixed the path with <literal>file:</literal>, then passed it to the URL constructor. This method was incompatible with Microsoft Windows Server because <literal>file:C:\...</literal> is not a valid file URL. This function has been corrected and the method of converting paths to URLs is now compatible with all supported platforms.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW

      Description

      Apache xml-commons resolver (1.1b1 shipped in lib/endorsed) does not correctly convert paths to URLs (using File.toURL or similar), instead simply putting "file:" on the front and passing it to the URL constructor. This does not work on Windows since "file:C:\..." is not a valid file URL, it should be "file:/C:/..." instead.

      This did not affect EAP 5.1.1 and earlier since out FileURLConnection code had incorrect URL deconstruction code, so the bugs cancelled out. That debug was fixed in JBCOMMON-106, triggered this one to be encountered.

      Upstream resolver 1.2 has a partial fix for this (see https://issues.apache.org/bugzilla/show_bug.cgi?id=28719), which handles basic Windows paths but still does not correctly handle UNC paths (\\host\share\...).

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  mbenitez Martha Benitez
                  Reporter:
                  jameslivingston James Livingston
                  Writer:
                  Russell Dickenson
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: