camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Resolved] (CAMEL-6548) XQueryBuilder will override any saxon Configuration provided
Date Sun, 14 Jul 2013 08:50:50 GMT


Claus Ibsen resolved CAMEL-6548.

       Resolution: Fixed
    Fix Version/s: 2.12.0

Thanks for the patch.

Saxon has changed its API in latest release so had to do a few changes.
> XQueryBuilder will override any saxon Configuration provided
> ------------------------------------------------------------
>                 Key: CAMEL-6548
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-saxon
>    Affects Versions: 2.11.2
>            Reporter: Niels Bertram
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.11.2, 2.12.0
> Sometimes one wants to register a custom extension function {{net.sf.saxon.lib.ExtensionFunctionDefinition}}
in the saxon xquery engine context.
> When providing {{XQueryBuilder.setConfiguration(Configuration configuration)}} with such
configuration, the method will set the context and also set the initialise flag to false (line
378). This will cause {{XQueryBuilder.initialize(Exchange exchange)}} to run next time the
builder is used.
> Unfortunately the initialize method on line 639 it will create a new saxon Configuration
regardless of what was set in the {{XQueryBuilder.setConfiguration()}} and renders this function
pretty much useless.
> The obvious solution to this problem is to check if the configuration is null before
creating a new saxon configuration.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message