IC51834: USE OF JAVA OR JAVASCRIPT FUNCTIONS IN XML MAPPING CAUSE CWSXM3110E ERRORS FROM XSLT PRIMITIVE

APAR status

• Closed as program error.

Error description

• If the XML mapper is used to construct an XML map which
  incorporates the use of Java or JavaScript functions
  then a CWSXM3110E error may be thrown from the XSLT
  mediation primitive. This is due to a limitation in the
  XSLT compiler being used by the XSLT mediation
  primitive which is not present in the Xalan XSLT compiler.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of WebSphere Enterprise Service Bus    *
  *                 and WebSphere Process Server v6.0.1 and      *
  *                 v6.0.2.0, using a Mediation Flow             *
  *                 Component which contains an XSLT mediation   *
  *                 primitive, and the XSL transform is          *
  *                 attempting to use Java or JavaScript         *
  *                 functions.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: When an XSLT mediation primitive uses   *
  *                      a WebSphere Integration Developer       *
  *                      generated XSL transform stylesheet      *
  *                      which makes use of Java or JavaScript   *
  *                      functions, the primitive may produce    *
  *                      a CWSXM3110E error message, with the    *
  *                      text: "Could not compile XSL            *
  *                      stylesheet", followed by one of a       *
  *                      number of more specific messages, for   *
  *                      example: "First argument to             *
  *                      non-static method <methodName> of       *
  *                      class <className> has an invalid        *
  *                      object reference".                      *
  ****************************************************************
  * RECOMMENDATION: If you encounter this problem, it is         *
  *                 recommended you install the fix pack which   *
  *                 contains the code fix.  This fix is          *
  *                 currently targeted to be included in         *
  *                 v6.0.2 Fix Pack 1 (v6.0.2.1).                *
  *                 Alternatively, you may manually              *
  *                 edit the generated stylesheet to circumvent  *
  *                 the problem.                                 *
  ****************************************************************
  The XSLTC compiling engine used in the XSLT primitive cannot
  process certain types of XSL operations that call Java
  functions.  The problem occurs because of differences in the
  way that parameter values are required in the extension
  function calls.  The fix associated with this APAR instructs
  the XSLT primitive to fall back to the Xalan engine whenever
  the problem would arise.
  
  As the Xalan engine does not perform as well as the XSLTC
  engine, if performance of XSLT processing is of particular
  priority to you, you may wish to construct your stylesheets
  to avoid Java or JavaScript.
  

Problem conclusion

• The only known side effect with this fix is that the
  performance of the Xalan transformation engine is not as
  good as the XSLTC engine.   Therefore as stated above, it
  may be desirable to you to avoid the use of Java or
  JavaScript methods within your stylesheets.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEB ESB FOR WIN

• Fixed component ID

  5724I8200

Applicable component levels

• R100 PSY

     UP

• R200 PSY

     UP