Uploaded image for project: 'Red Hat build of Apache Camel for Spring Boot'
  1. Red Hat build of Apache Camel for Spring Boot
  2. CSB-3682

Exchange property "CamelXsltError" appears empty, when a incorrect transformation is attempted with XSLT and Saxon

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Normal Normal
    • None
    • CSB-4.0
    • Camel
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      • A reproducer is attached.

      The steps:
      $ unzip jira-reproducer.zip
      $ cd jira-reproducer
      $ mvn clean spring-boot:run

      The output:

      • You will see on the output

      ... CamelXsltError=|| 

      • What is expected to be on the output

      The header "CamelXsltError" should contain the fragment that contains the error, as before
      For example, on previous versions, with the same code:

      ... CamelXsltError=|<xsl:text>This is the message I'm looking for.</xsl:text>|

      Show
      A reproducer is attached. The steps: $ unzip jira-reproducer.zip $ cd jira-reproducer $ mvn clean spring-boot:run The output: You will see on the output ... CamelXsltError=||  What is expected to be on the output The header "CamelXsltError" should contain the fragment that contains the error, as before For example, on previous versions, with the same code: ... CamelXsltError=|<xsl:text>This is the message I'm looking for.</xsl:text>|
    • Critical
    • Very Likely
    • 0

      In prior release of Camel (Fuse 7.x | Camel 2.2x) the content of our "message" when there was an abnormal termination, was delivered by the exchange property named ${exchangeProperty.CamelXsltError}
      This property has disappeared from the Exchange, although it is still documented for the xslt-saxon component.
      We cannot see other header or property with the info either. This seems like a major bug.

       

        3. screenshot-1.png
          131 kB
          Luigi De Masi
        4. screenshot-2.png
          146 kB
          Luigi De Masi
        5. screenshot-3.png
          113 kB
          Luigi De Masi

          1.
          		 Fix Exchange property "CamelXsltError" appears empty, when a transformation is attempted with XSLT and Saxon - Saxon Sub-task Closed Normal Luigi De Masi
          2.
          		 Validate Exchange property "CamelXsltError" appears empty, when a transformation is attempted with XSLT and Saxon - Saxon Sub-task Closed Normal Unassigned

              ldemasi Luigi De Masi
              rhn-support-anarvaez Alfredo Narvaez
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: