Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-1520

XMLFilePlugin fails to read the configuration if its path contains unicode characters

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 4.6.1.CP14
    • 4.6.1.CP13
    • Common
    • None

    Description

      If the path to arjuna configuration file contains unicode characters the XMLFilePlugin class fails to read it. XMLFilePlugin then calls DocumentBuilder#parse(String uri) which expects the argument being a valid URI. As long as URI spec does not support unicode chars the filename in XMLFilePlugin needs to be converted to a valid URI without any unicode/special characters.

      Note that FileLocator.locateFile performs some conversions over the filename, but these do not seem to be enough.

      This bug prevents Arjuna from starting which subsequently prevents EAP from starting.

      Attachments

        Issue Links

          Activity

            People

              istudens@redhat.com Ivo Studensky
              istudens@redhat.com Ivo Studensky
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: