To clarify, the hang occurs In the jaxb, not the XSLT, when it tries to
unmarshal the XML into a Java Object.

Blueprint:

<unmarshal>
<jaxb prettyPrint="false" contextPath="our.model"/>
</unmarshal>

Here's a snippet of the XML it's trying to unmarshal into a Java bean.



<foobar xmlns:fn="http://www.w3.org/2005/xpath-functions";
xmlns:fo="http://www.w3.org/1999/XSL/Format";
xmlns:foo="http://whatever";
xmlns:xs="http://www.w3.org/2001/XMLSchema";>    <bar>
        <foo>false</foo>
    </bar>
</foobar>

where foo is defined like this in the bar bean.

So the value being unmarshalled is 'false' instead of an int.

I could understand and expect an error being thrown, but it's a silent hang.
Is any jaxb config available to deal with things like this?


    @XmlElement(name="foo")
    private int foo;

... down below in getters and setters

    public int getFoo()  { return foo; }
    public void setFoo(int param)  { foo = param; }



On Mon, Sep 23, 2024 at 12:48 PM Darrel Riekhof (EXT) <
darrel.riek...@mantech.com> wrote:

> 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.

Reply via email to