[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlbeans-dev
Subject:    [jira] Resolved: (XMLBEANS-373) pluggable XPath/XQuery engine
From:       "Wing Yew Poon (JIRA)" <xmlbeans-dev () xml ! apache ! org>
Date:       2009-11-02 20:40:59
Message-ID: 1308460468.1257194459888.JavaMail.jira () brutus
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/XMLBEANS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Wing Yew Poon resolved XMLBEANS-373.
------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: TBD)
                   Version 2.4 

This enhancement went into XMLBeans 2.4.0.

> pluggable XPath/XQuery engine support
> -------------------------------------
> 
> Key: XMLBEANS-373
> URL: https://issues.apache.org/jira/browse/XMLBEANS-373
> Project: XMLBeans
> Issue Type: Improvement
> Components: XPath
> Affects Versions:  Version 2.3
> Reporter: Wing Yew Poon
> Assignee: Wing Yew Poon
> Fix For: Version 2.4 
> 
> Attachments: delegate_diff3.txt
> 
> 
> This is an enhancement proposal.
> Currently, XMLBeans looks for certain engines in certain orders to process \
> XPath/XQuery expressions. In particular, it searches for the Saxon XQuery engine. \
> There has been a request (XMLBEANS-366) to support the use of JXPath for processing \
> XPath expressions. The patch from the user changes the engine lookup logic to add \
> looking for JXPath if Saxon is not found. I propose to make the choice of engine \
> more pluggable instead of hardcoding logic to lookup Saxon/JXPath/etc.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]