[
https://issues.apache.org/jira/browse/ODE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jürgen Schumacher updated ODE-429:
----------------------------------
Attachment: ode-xpath1-jaxp-2008-11-24.patch
Here is an updated version of the patch:
- conversion workaround to make evaluation of toplevel string/date/number
functions as RValue work
- adapted to latest changes in trunk (rev 719808)
- patch in XPath20ExpressionRuntimes that have became a bit greedy when
registering Saxon as the XPathFactory for the default DOM object model.
- patch BPELCompilers to survive missing Saxon libs when registering the XQuery
expression compiler, too.
Any feedback is highly appreciated.
Regards,
Juergen.
> Patch to make Saxon and Jaxen optional for XPath 1.0 processing
> ---------------------------------------------------------------
>
> Key: ODE-429
> URL: https://issues.apache.org/jira/browse/ODE-429
> Project: ODE
> Issue Type: Improvement
> Components: BPEL Compilation/Parsing, BPEL Runtime
> Affects Versions: 2.0
> Reporter: Jürgen Schumacher
> Fix For: 2.0
>
> Attachments: ode-xpath1-jaxp-2008-11-24.patch, ode-xpath1-jaxp.patch
>
>
> See
> http://ode.markmail.org/search/?q=saxon+jaxen#query:saxon%20jaxen+page:1+mid:3sramehxzsfceg76+state:results
>
> This patch adds classes for XPath 1.0 compilation and evaluation based only
> on JAXP interfaces, independent on any specific JAXP implementation. It's
> selected as a fallback in the BPELCompilers if instantiating the existing
> XPath-1.0-implementation based on Jaxen (and Saxon for doXslTransform) fails.
> This enables us to remove Jaxen and Saxon from the classpath which are not
> accepted by the Eclipse foundation because of legal issues (code provenance
> problems...). So the default behaviour of ODE should be the same as without
> these changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
