We've recently upgraded to Camel 4.7.0 running on Karaf 4.4.6
Ran into a nasty bug during the XSLT transform called from a blueprint that
didn't happen on our much older camel/karaf combo from RH Fuse 7.1.2
We call the transform like this in our XML blueprints:
<to uri="xslt:file:path/to/xslt/file/foo.xslt"/>
We found the problem by just chopping out xslt until it ran without
hanging.
Here's the XSLT that causes the silent hang.
This causes camel process on karaf to hang forever:
<xsl:variable name="foo" select="fn:normalize-space(foo)"/>
This doesn't hang:
<xsl:variable name="fooRaw"
select="fn:normalize-space(foo)"/><xsl:variable name="foo">
<xsl:choose> <xsl:when test="$fooRaw= 'true'">1</xsl:when>
<xsl:when test="$fooRaw= 'false'">0</xsl:when>
</xsl:choose></xsl:variable>
So passing a 'true' or 'false' when it expects a 1 or 0 causes the hang in
our use case.
I was thinking of creating a minimal use case and submitting a Jira here,
but not sure of the process and looking for guidance.
Darrel
--
This e-mail and any attachments are intended only for the use of the
addressee(s) named herein and may contain proprietary information. If you
are not the intended recipient of this e-mail or believe that you received
this email in error, please take immediate action to notify the sender of
the apparent error by reply e-mail; permanently delete the e-mail and any
attachments from your computer; and do not disseminate, distribute, use, or
copy this message and any attachments.
