Easy-WSDL

Xalan implementation is redefined according to JVM specific fields

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 2.1, 2.2, 2.3
  • Fix Version/s: 2.3
  • Component/s: Easy-Schema, XSD2XSML
  • Security Level: Public
  • Description:
    Hide

    Xalan implementation is choosen in different portions of easyWSDL using the following code :

    if (System.getProperty("java.vendor").indexOf("Sun") != -1){ System.setProperty("javax.xml.transform.TransformerFactory", "com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl"); }else if (System.getProperty("java.vendor").indexOf("IBM") != -1){ System.setProperty("javax.xml.transform.TransformerFactory", "org.apache.xalan.processor.TransformerFactoryImpl"); }

    Because of this code, we cannot use a less buggy Xalan implementation using the endorsed mechanism.

    Show
    Xalan implementation is choosen in different portions of easyWSDL using the following code : if (System.getProperty("java.vendor").indexOf("Sun") != -1){ System.setProperty("javax.xml.transform.TransformerFactory", "com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl"); }else if (System.getProperty("java.vendor").indexOf("IBM") != -1){ System.setProperty("javax.xml.transform.TransformerFactory", "org.apache.xalan.processor.TransformerFactoryImpl"); } Because of this code, we cannot use a less buggy Xalan implementation using the endorsed mechanism.
  • Environment:
    PetalsESB 3.1, Petals-SE-XSLT 2.4-SNAPSHOT, Petals-SE-BPEL, large XSL stylesheets.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
mjambert added a comment - Wed, 18 Aug 2010 - 09:24:33 +0200

Apparently, these hacks were introduced (and commited) by the consulting team who wanted to make petals/easywsdl work on an IBM JVM.

As far as I know, this operation mode (petals under ibm JVM) is never tested.

Is it used by any client ?
Is it officially supported ?

Show
mjambert added a comment - Wed, 18 Aug 2010 - 09:24:33 +0200 Apparently, these hacks were introduced (and commited) by the consulting team who wanted to make petals/easywsdl work on an IBM JVM. As far as I know, this operation mode (petals under ibm JVM) is never tested. Is it used by any client ? Is it officially supported ?
Hide
Permalink
mjambert added a comment - Wed, 18 Aug 2010 - 09:33:49 +0200

Problem also detected in easycommons (duplicate code).

Show
mjambert added a comment - Wed, 18 Aug 2010 - 09:33:49 +0200 Problem also detected in easycommons (duplicate code).
Hide
Permalink
mjambert added a comment - Wed, 18 Aug 2010 - 09:36:55 +0200

Suspicious TransformerFactory overriden in easybpel tests as well.

Show
mjambert added a comment - Wed, 18 Aug 2010 - 09:36:55 +0200 Suspicious TransformerFactory overriden in easybpel tests as well.
Hide
Permalink
Charles Casadei added a comment - Wed, 18 Aug 2010 - 09:55:45 +0200

The transformer factory can be overriden using a system property (see this page : http://xml.apache.org/xalan-j/usagepatterns.html )

Even if we had customer with an IBM JVM, we can use a system property to fix the problem addressed by the previous code.

Show
Charles Casadei added a comment - Wed, 18 Aug 2010 - 09:55:45 +0200 The transformer factory can be overriden using a system property (see this page : http://xml.apache.org/xalan-j/usagepatterns.html ) Even if we had customer with an IBM JVM, we can use a system property to fix the problem addressed by the previous code.
Hide
Permalink
mjambert added a comment - Wed, 18 Aug 2010 - 09:59:37 +0200

OK.

Show
mjambert added a comment - Wed, 18 Aug 2010 - 09:59:37 +0200 OK.

People

Dates

  • Created:
    Tue, 17 Aug 2010 - 11:37:22 +0200
    Updated:
    Fri, 1 Oct 2010 - 09:00:38 +0200
    Resolved:
    Wed, 18 Aug 2010 - 11:48:54 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.