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

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 4.6.1.CP13
    • Fix Version/s: 4.6.1.CP14
    • Component/s: Common
    • Labels:
      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  istudens Ivo Studensky
                  Reporter:
                  istudens Ivo Studensky
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: