Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 14 Jul 2013 08:20:49 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12657599.1373737660762.46980.1373790049058@arcas>
In-Reply-To: <JIRA.12657599.1373737660762@arcas>
References: <JIRA.12657599.1373737660762@arcas>
Subject: [jira] [Commented] (CAMEL-6548) XQueryBuilder will override any
 saxon Configuration provided
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707985#comment-13707985 ] 

Claus Ibsen commented on CAMEL-6548:
------------------------------------

Willem I am working on this, there is some changes needed on trunk the patch doesn't work with.
                
> XQueryBuilder will override any saxon Configuration provided
> ------------------------------------------------------------
>
>                 Key: CAMEL-6548
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6548
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-saxon
>    Affects Versions: 2.11.2
>            Reporter: Niels Bertram
>            Assignee: Willem Jiang
>            Priority: Minor
>
> 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: http://www.atlassian.com/software/jira