Petals SE XSLT

[SE-XSLT] Can't import properly XSL stylesheet with imports

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 2.3.2
  • Fix Version/s: 2.4
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    When using XSL stylesheet with imports on the SE-XSLT, if the import is a fully qualified url like http://host:port/myStyleSheet.xsl everything is fine. But if you try to use relative path, everything goes wrong, the component expects to find the XSL stylesheet in the $PETALS_HOME/bin directory.

    Show
    When using XSL stylesheet with imports on the SE-XSLT, if the import is a fully qualified url like http://host:port/myStyleSheet.xsl everything is fine. But if you try to use relative path, everything goes wrong, the component expects to find the XSL stylesheet in the $PETALS_HOME/bin directory.
  • Environment:
    Petals ESB 3.1
    Petals SE-XSLT trunk
    Petals-SE-EIP trunk
    Petals-BC-SOAP trunk

Attachments

  1. File
    AD003_Declencheur_vers_IDT-MP0118_01.01.xsl
    (2 kB)
    Charles Casadei
    Wed, 28 Jul 2010 - 14:17:28 +0200
  2. File
    AD003_IDT-MP0118-Result_vers_InfosMissionLiteListe_01.01.xsl
    (3 kB)
    Charles Casadei
    Wed, 28 Jul 2010 - 14:17:28 +0200
  3. File
    concat_IDT_IdMission.xsl
    (1 kB)
    Charles Casadei
    Wed, 28 Jul 2010 - 14:19:28 +0200
  4. XML File
    conf.xml
    (0.5 kB)
    Charles Casadei
    Wed, 28 Jul 2010 - 15:24:03 +0200
  5. File
    date_declencheur_vers_grid_IDT.xsl
    (1 kB)
    Charles Casadei
    Wed, 28 Jul 2010 - 14:19:28 +0200
  6. Zip Archive
    petals-bc-soap-4.0.3-20100704.073518-7.zip
    (16.83 MB)
    Charles Casadei
    Wed, 28 Jul 2010 - 14:30:04 +0200
  7. Zip Archive
    petals-se-eip-2.5-20100610.103318-7.zip
    (4.54 MB)
    Charles Casadei
    Wed, 28 Jul 2010 - 14:30:04 +0200
  8. Zip Archive
    petals-se-xslt-2.3.3-SNAPSHOT.zip
    (6.12 MB)
    Charles Casadei
    Wed, 28 Jul 2010 - 14:16:14 +0200
  9. File
    requeteCleValeur.xsl
    (0.5 kB)
    Charles Casadei
    Wed, 28 Jul 2010 - 14:19:28 +0200
  10. Zip Archive
    sa-AD003-RecupIDsMissionsSigma-1.0.0-SNAPSHOT.zip
    (89 kB)
    Charles Casadei
    Wed, 28 Jul 2010 - 14:16:14 +0200

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Charles Casadei added a comment - Wed, 28 Jul 2010 - 15:36:19 +0200

Reproduction :

  • configure the SE-XSLT to use the conf.xml file (which is already OK to use our database)
  • start petals
  • deploy all the components
  • deploy the SA.
    >>> woops
  • undeploy the SA
  • put all the XSL & XSD schemes in the $PETALS_HOME/bin directory
  • deploy the SA
    >>> OK
Show
Charles Casadei added a comment - Wed, 28 Jul 2010 - 15:36:19 +0200 Reproduction :
  • configure the SE-XSLT to use the conf.xml file (which is already OK to use our database)
  • start petals
  • deploy all the components
  • deploy the SA. >>> woops
  • undeploy the SA
  • put all the XSL & XSD schemes in the $PETALS_HOME/bin directory
  • deploy the SA >>> OK
Hide
Permalink
Vincent Zurczak added a comment - Wed, 28 Jul 2010 - 15:48:47 +0200

When you say "trunk version", what is the snapshot version indicated in the component 's build?
The life cycle of the component was changed last week, and if such an error had to occur now, it would occur during the start phase.

Anyway, I take a look at it.

Show
Vincent Zurczak added a comment - Wed, 28 Jul 2010 - 15:48:47 +0200 When you say "trunk version", what is the snapshot version indicated in the component 's build? The life cycle of the component was changed last week, and if such an error had to occur now, it would occur during the start phase. Anyway, I take a look at it.
Hide
Permalink
Vincent Zurczak added a comment - Wed, 28 Jul 2010 - 15:50:32 +0200

OK, 2.3.3-SNAPSHOT.
Since yesterday, we are on the 2.4-SNAPSHOT.

Show
Vincent Zurczak added a comment - Wed, 28 Jul 2010 - 15:50:32 +0200 OK, 2.3.3-SNAPSHOT. Since yesterday, we are on the 2.4-SNAPSHOT.
Hide
Permalink
Vincent Zurczak added a comment - Wed, 28 Jul 2010 - 16:06:53 +0200

I don't know how to do this: "configure the SE-XSLT to use the conf.xml file".
Any hint on this would be helpful.

Besides, on deployment, I have an exception from EasyWSDL, about a timeout when installing the EIP.
I cannot access http://172.20.222.235/svn/ESB/transverse/trunk/_SOA_Artefacts/pivot/SI/Transverse/objet/EnvVeolia_01.xsd

Anyway, I have updated the SA to only keep the XSLT SU.
The bug is confirmed.

Show
Vincent Zurczak added a comment - Wed, 28 Jul 2010 - 16:06:53 +0200 I don't know how to do this: "configure the SE-XSLT to use the conf.xml file". Any hint on this would be helpful. Besides, on deployment, I have an exception from EasyWSDL, about a timeout when installing the EIP. I cannot access http://172.20.222.235/svn/ESB/transverse/trunk/_SOA_Artefacts/pivot/SI/Transverse/objet/EnvVeolia_01.xsd Anyway, I have updated the SA to only keep the XSLT SU. The bug is confirmed.
Hide
Permalink
Vincent Zurczak added a comment - Wed, 28 Jul 2010 - 16:29:42 +0200

I fixed the resolving issue.
However, I got another error then, and I do not known whether the error is related to the XSLT SE or to the SU.

ERREUR : 'Le premier argument de la fonction Java non static 'getTranscoAppliPivot' n'est pas une rÚfÚrence d'objet valide.'
ERREUR BLOQUANTE : 'Impossible de compiler la feuille de style'
[Petals.Container.ServiceAssemblyLifeCycle.sa-AD003-RecupIDsMissionsSigma-1.0.0-SNAPSHOT]-SEVERE 2010-07-28 16:20:45,828 Failed to start the Service Unit 'su-XSLT-AD003-TransfoOut-provide-1.0.0-SNAPSHOT'

Is your XSL stylesheet right?
Or is it the SE the responsible?

Show
Vincent Zurczak added a comment - Wed, 28 Jul 2010 - 16:29:42 +0200 I fixed the resolving issue. However, I got another error then, and I do not known whether the error is related to the XSLT SE or to the SU. ERREUR : 'Le premier argument de la fonction Java non static 'getTranscoAppliPivot' n'est pas une rÚfÚrence d'objet valide.' ERREUR BLOQUANTE : 'Impossible de compiler la feuille de style' [Petals.Container.ServiceAssemblyLifeCycle.sa-AD003-RecupIDsMissionsSigma-1.0.0-SNAPSHOT]-SEVERE 2010-07-28 16:20:45,828 Failed to start the Service Unit 'su-XSLT-AD003-TransfoOut-provide-1.0.0-SNAPSHOT' Is your XSL stylesheet right? Or is it the SE the responsible?
Hide
Permalink
Vincent Zurczak added a comment - Wed, 28 Jul 2010 - 17:00:54 +0200

Commit # 15449
The error that appears then would be another issue, if it is an issue.
Can you confirm you do not have errors about import resolution anymore?

Show
Vincent Zurczak added a comment - Wed, 28 Jul 2010 - 17:00:54 +0200 Commit # 15449 The error that appears then would be another issue, if it is an issue. Can you confirm you do not have errors about import resolution anymore?
Hide
Permalink
Charles Casadei added a comment - Thu, 29 Jul 2010 - 09:26:44 +0200

I will check for the resolution of this issue on monday, since I can't access any of the OW2 repository.

For the second issue, it OK. We use a proprietary library endorsed on the SE-XSLT component. If this library is not present or can't access to the database storing the transcodifications, you'll get errors. So there is no need to create another jira issue for this problem.

Show
Charles Casadei added a comment - Thu, 29 Jul 2010 - 09:26:44 +0200 I will check for the resolution of this issue on monday, since I can't access any of the OW2 repository. For the second issue, it OK. We use a proprietary library endorsed on the SE-XSLT component. If this library is not present or can't access to the database storing the transcodifications, you'll get errors. So there is no need to create another jira issue for this problem.
Hide
Permalink
Christophe DENEUX added a comment - Thu, 29 Jul 2010 - 16:48:04 +0200

Can you set the attribute 'Fix version/s'

Show
Christophe DENEUX added a comment - Thu, 29 Jul 2010 - 16:48:04 +0200 Can you set the attribute 'Fix version/s'
Hide
Permalink
Vincent Zurczak added a comment - Thu, 29 Jul 2010 - 16:52:13 +0200

JIRA does not ask for the fix version when we change its state to "resolved".
It is only asked when you close the bug.

Anyway, I edited the bug manually.

Show
Vincent Zurczak added a comment - Thu, 29 Jul 2010 - 16:52:13 +0200 JIRA does not ask for the fix version when we change its state to "resolved". It is only asked when you close the bug. Anyway, I edited the bug manually.

People

Dates

  • Created:
    Wed, 28 Jul 2010 - 14:14:53 +0200
    Updated:
    Wed, 4 Aug 2010 - 16:46:13 +0200
    Resolved:
    Wed, 28 Jul 2010 - 17:00:54 +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.