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.

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