Petals SE XSLT

Should be able to work with the same XSLT engine in two different versions

Details

  • Type: Improvement Request Improvement Request
  • Status: In Progress In Progress
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.7.3
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    The SE XSLT accepts SL to provide XSLT engine. SO it is possible to configure several SLs providing the same XSLT engine in different versions.

    At SU level, the XSLT engine to use is defined through its TransformerFactory class name, that is the same for the different versions of the XSLT engine.

    So, a mechanism to select with precision the XSLT engine must be added add SU level.

    Show
    The SE XSLT accepts SL to provide XSLT engine. SO it is possible to configure several SLs providing the same XSLT engine in different versions. At SU level, the XSLT engine to use is defined through its TransformerFactory class name, that is the same for the different versions of the XSLT engine. So, a mechanism to select with precision the XSLT engine must be added add SU level.
  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Thu, 9 Jul 2015 - 11:05:54 +0200
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Assignee Vincent Zurczak [ vzurczak ] Christophe DENEUX [ cdeneux ]
Christophe DENEUX made changes - Thu, 9 Jul 2015 - 11:05:57 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Thu, 9 Jul 2015 - 11:09:13 +0200

No mechanism is available to have more precision. To implement such use case, it is needed to create your own SL with the XSLT engine where you have changed its Java package name. So the TransformerFactory will have different names, and each SU could be used it own XSLT engine version.

Just add documentation and an integration test about this use case to solve this issue.

Show
Christophe DENEUX added a comment - Thu, 9 Jul 2015 - 11:09:13 +0200 No mechanism is available to have more precision. To implement such use case, it is needed to create your own SL with the XSLT engine where you have changed its Java package name. So the TransformerFactory will have different names, and each SU could be used it own XSLT engine version. Just add documentation and an integration test about this use case to solve this issue.
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
34s
1
Christophe DENEUX
Thu, 9 Jul 2015 - 11:05:54 +0200
Open Open In Progress In Progress
3s
1
Christophe DENEUX
Thu, 9 Jul 2015 - 11:05:57 +0200



People

Dates

  • Created:
    Thu, 9 Jul 2015 - 11:05:20 +0200
    Updated:
    Thu, 9 Jul 2015 - 11:09:13 +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.