ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Riou (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ODE-429) Patch to make Saxon and Jaxen optional for XPath 1.0 processing
Date Wed, 17 Dec 2008 17:41:44 GMT

    [ https://issues.apache.org/jira/browse/ODE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657463#action_12657463
] 

Matthieu Riou commented on ODE-429:
-----------------------------------

I've tried to apply the patch but the following package is missing:

org.apache.ode.bpel.compiler.v1.xpath10.jaxp

I have the v2 version of it but not the v1, which leads to several compilation error. I'm
guessing you forgot to add the directory before doing a "svn diff" :)

Other than that the patch looks good, I'll commit it as soon as you give me the whole thing.
Thanks for your patience.

> 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-2008-11-25.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.


Mime
View raw message