Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-25485

The XSLT library used by JIRA depends upon the order that xalan and saxon are loaded by the ClassLoader

XMLWordPrintable

    • 4.02
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 04 December 2017

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.

      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 04 December 2017 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

      We ship with two XSLT libraries: xalan and saxon. The way that TransformerFactory finds an implementation (as we ship now) is too look for META-INF/services/javax.xml.transform.TransformerFactory on the classpath and then use the class listed therein (ala ServiceLoader). The problem is that both xalan and saxon ship with a META-INF/services/javax.xml.transform.TransformerFactory file which means that the library chosen to implement TransformerFactory depends on which of the two files the classloader decides to return first.

      This basically means that the XSLT library used in JIRA is completely dependent on the classloader which in turn is probably dependent on the order that jar files are listed in the file system. This is not a good situation to be in.

              Unassigned Unassigned
              bbain bain
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: