You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Mark Ford (JIRA)" <ji...@apache.org> on 2009/07/17 17:24:14 UTC
[jira] Created: (ODE-638) Incorrect default expression language for
property aliases
Incorrect default expression language for property aliases
----------------------------------------------------------
Key: ODE-638
URL: https://issues.apache.org/jira/browse/ODE-638
Project: ODE
Issue Type: Bug
Components: BPEL Compilation/Parsing
Affects Versions: 1.3.2
Reporter: Mark Ford
If a property alias does not define a query language then the default should be XPath 1.0 as per the WS-BPEL 2.0 spec. BpelCompiler.compile(PropertyAlias) uses the same compileExpr(Expression) call as other expressions so the default language becomes whatever the default is for the process definition or XPath 1.0 if not defined.
I found this problem by setting a default expression to XQuery in my process def. This results in an error at execution since the XQuery compiler inserts a variable declaration for $ode:pid which doesn't resolve in the property alias context.
One workaround is to add the queryLanguage attribute to each propertyAlias. Another workaround is to not define a default expression language for the process.
Time permitting, I'll add a test case or patch at some point.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-638) Incorrect default expression language
for property aliases
Posted by "David Carver (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854780#action_12854780 ]
David Carver commented on ODE-638:
----------------------------------
Mark any chance you can provide a test case to replicate? I know it's been a while since you filled the bug.
> Incorrect default expression language for property aliases
> ----------------------------------------------------------
>
> Key: ODE-638
> URL: https://issues.apache.org/jira/browse/ODE-638
> Project: ODE
> Issue Type: Bug
> Components: BPEL Compilation/Parsing
> Affects Versions: 1.3.2
> Reporter: Mark Ford
> Assignee: Karthick Sankarachary
> Fix For: 1.3.5
>
>
> If a property alias does not define a query language then the default should be XPath 1.0 as per the WS-BPEL 2.0 spec. BpelCompiler.compile(PropertyAlias) uses the same compileExpr(Expression) call as other expressions so the default language becomes whatever the default is for the process definition or XPath 1.0 if not defined.
> I found this problem by setting a default expression to XQuery in my process def. This results in an error at execution since the XQuery compiler inserts a variable declaration for $ode:pid which doesn't resolve in the property alias context.
> One workaround is to add the queryLanguage attribute to each propertyAlias. Another workaround is to not define a default expression language for the process.
> Time permitting, I'll add a test case or patch at some point.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-638) Incorrect default expression language for
property aliases
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexis Midon updated ODE-638:
-----------------------------
Fix Version/s: 1.3.5
Assignee: Karthick Sankarachary
> Incorrect default expression language for property aliases
> ----------------------------------------------------------
>
> Key: ODE-638
> URL: https://issues.apache.org/jira/browse/ODE-638
> Project: ODE
> Issue Type: Bug
> Components: BPEL Compilation/Parsing
> Affects Versions: 1.3.2
> Reporter: Mark Ford
> Assignee: Karthick Sankarachary
> Fix For: 1.3.5
>
>
> If a property alias does not define a query language then the default should be XPath 1.0 as per the WS-BPEL 2.0 spec. BpelCompiler.compile(PropertyAlias) uses the same compileExpr(Expression) call as other expressions so the default language becomes whatever the default is for the process definition or XPath 1.0 if not defined.
> I found this problem by setting a default expression to XQuery in my process def. This results in an error at execution since the XQuery compiler inserts a variable declaration for $ode:pid which doesn't resolve in the property alias context.
> One workaround is to add the queryLanguage attribute to each propertyAlias. Another workaround is to not define a default expression language for the process.
> Time permitting, I'll add a test case or patch at some point.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.