Petals SE Talend

The SE Talend does not run anymore on Petals ESB 4.1+

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 1.0.2
  • Fix Version/s: 1.1.0
  • Component/s: None
  • Security Level: Public
  • Description:

    The error "Saxon TransformerFactory not found" occurs running Talend job on SE Talend 1.1.0-SNAPSHOT and Petals ESB 4.1+ (4.2-SNAPSHOT).

  • Environment:
    Petals ESB 4.1+

Issue Links

Depends
 

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Victor NOËL added a comment - Wed, 8 Jul 2015 - 14:18:01 +0200

When Saxon is removed, there won't be any problem anymore: one will use a SL to choose Saxon if desired.

Show
Victor NOËL added a comment - Wed, 8 Jul 2015 - 14:18:01 +0200 When Saxon is removed, there won't be any problem anymore: one will use a SL to choose Saxon if desired.
Hide
Permalink
Christophe DENEUX added a comment - Tue, 24 Sep 2013 - 10:35:40 +0200

Reopen because PETALSESBCONT-255 has been reopen

Show
Christophe DENEUX added a comment - Tue, 24 Sep 2013 - 10:35:40 +0200 Reopen because PETALSESBCONT-255 has been reopen
Hide
Permalink
Christophe DENEUX added a comment - Mon, 15 Apr 2013 - 18:19:39 +0200 - edited

Talend's job are run in a dedicated classloader inherited from the system classloader to avoid conflicts between libraries provided by Talend and libraries provided by Petals.
As, the use of Saxon TransformerFactory is defined by a system property on the command line starting Petals, Saxon should be included in the classloader mentioned here-above. This is not the best solution that is to remove the system property defining the TransformerFactory to use. As Saxon is included in the Petals ESB classloader, it will be automatically taken into account (see Java SPI).

This problem will be solved by PETALSESBCONT-255

Show
Christophe DENEUX added a comment - Mon, 15 Apr 2013 - 18:19:39 +0200 - edited Talend's job are run in a dedicated classloader inherited from the system classloader to avoid conflicts between libraries provided by Talend and libraries provided by Petals. As, the use of Saxon TransformerFactory is defined by a system property on the command line starting Petals, Saxon should be included in the classloader mentioned here-above. This is not the best solution that is to remove the system property defining the TransformerFactory to use. As Saxon is included in the Petals ESB classloader, it will be automatically taken into account (see Java SPI). This problem will be solved by PETALSESBCONT-255

People

Dates

  • Created:
    Mon, 15 Apr 2013 - 18:09:39 +0200
    Updated:
    Tue, 6 Oct 2015 - 11:12:39 +0200
    Resolved:
    Tue, 6 Oct 2015 - 11:12:06 +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.