Petals Distribution

Override the embedded Saxon XSLT engine

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.0.0, 4.1.0, 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.4
  • Fix Version/s: 5.0.0-M1
  • Component/s: Components, Container
  • Security Level: Public
  • Description:
    Hide

    Previously to Petals 4.0, if a need of XSLT 2.0 occurs at SE XSLT level, you will use the Petals SE XSLT with Saxon provided as shared library. Since Petals 4, Saxon HE 9.2.0.6 was defined as the default XSLT engine of Petals ESB. We select it instead of Xalan to provide an XSLT 2.0.

    Since Saxon 9.2, Saxon product packages was reviewed, and some XSL features are no more available in the Saxon open source edition because they was moved into commercial editions (PE and EE).

    We should be able to override the default Saxon to use your own edition and/or version, at least on Petals SE XSLT.

    Show
    Previously to Petals 4.0, if a need of XSLT 2.0 occurs at SE XSLT level, you will use the Petals SE XSLT with Saxon provided as shared library. Since Petals 4, Saxon HE 9.2.0.6 was defined as the default XSLT engine of Petals ESB. We select it instead of Xalan to provide an XSLT 2.0. Since Saxon 9.2, Saxon product packages was reviewed, and some XSL features are no more available in the Saxon open source edition because they was moved into commercial editions (PE and EE). We should be able to override the default Saxon to use your own edition and/or version, at least on Petals SE XSLT.
  • Environment:
    -

Issue Links

Activity

Hide
Victor NOËL added a comment - Wed, 8 Jul 2015 - 16:38:58 +0200

Now the XSLT Engine is configurable using a SL (or it will use the Java default one, i.e. Xalan 2.7.0)

Show
Victor NOËL added a comment - Wed, 8 Jul 2015 - 16:38:58 +0200 Now the XSLT Engine is configurable using a SL (or it will use the Java default one, i.e. Xalan 2.7.0)
Hide
Victor NOËL added a comment - Wed, 8 Jul 2015 - 14:19:51 +0200

There won't be any more need for that when Saxon is removed: one will use a SL to choose the version of Saxon to use, and Xalan will be used by default.

Show
Victor NOËL added a comment - Wed, 8 Jul 2015 - 14:19:51 +0200 There won't be any more need for that when Saxon is removed: one will use a SL to choose the version of Saxon to use, and Xalan will be used by default.
Hide
Christophe DENEUX added a comment - Thu, 2 Jul 2015 - 17:49:42 +0200

svn#37404 merged in trunk

Show
Christophe DENEUX added a comment - Thu, 2 Jul 2015 - 17:49:42 +0200 svn#37404 merged in trunk
Hide
Christophe DENEUX added a comment - Thu, 2 Jul 2015 - 15:44:10 +0200 - edited

The integration tests of SE XSLT have been improved to use not only the Xalan XSLT engine but also the embedded Saxon HE XSLT engine (svn#37404, in branch petals-4.3.x). The test about the custom Java function returns an error due to the extensibility not supported by Saxon HE. It should work with Saxon B 9.0.0.8 if we can override Saxon.

Show
Christophe DENEUX added a comment - Thu, 2 Jul 2015 - 15:44:10 +0200 - edited The integration tests of SE XSLT have been improved to use not only the Xalan XSLT engine but also the embedded Saxon HE XSLT engine (svn#37404, in branch petals-4.3.x). The test about the custom Java function returns an error due to the extensibility not supported by Saxon HE. It should work with Saxon B 9.0.0.8 if we can override Saxon.

People

Dates

  • Created:
    Thu, 2 Jul 2015 - 11:46:35 +0200
    Updated:
    Wed, 8 Jul 2015 - 16:38:58 +0200
    Resolved:
    Wed, 8 Jul 2015 - 16:38:58 +0200