[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: BP-129: XPath Context Undefined
Assigned: http://www.osoa.org/jira/browse/BP-129
-----Original Message-----
From: Dieter Koenig1 [mailto:dieterkoenig@de.ibm.com]
Sent: Monday, October 19, 2009 10:54
To: bpel4people@lists.oasis-open.org
Subject: [bpel4people] New Issue: XPath Context Undefined
Target:
WS-HumanTask 1.1 CD 05 revision 9
BPEL4People 1.1 CD 05 revision 2
Description:
When XPath 1.0 is used as an Expression Language in BPEL4People or WS-HumanTask language elements then the XPath context is undefined.
The following proposal is inspired by WS-BPEL 2.0 section 8.2.4 (
http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html#_Ref130811481
).
Proposal:
In the WS-HumanTask specification, add a new section:
========================================
2.6 Default use of XPath 1.0 as an Expression Language The XPath 1.0 specification [XPATH 1.0] defines the context in which an XPath expression is evaluated. When XPath 1.0 is used as an Expression Language in WS-HumanTask language elements then the XPath context is initialized as follows:
-- Context node: none
-- Context position: none
-- Context size: none
-- Variable bindings: none
-- Function library: Core XPath 1.0 and WS-HumanTask functions MUST be available and processor-specific functions MAY be available
-- Namespace declaration: all in-scope namespace declarations from the enclosing element
Note that XPath 1.0 explicitly requires that any element or attribute used in an XPath expression that does not have a namespace prefix must be treated as being namespace unqualified. As a result, even if there is a default namespace defined on the enclosing element, the default namespace will not be applied.
========================================
In the BPEL4People 1.1 specification, add a new section:
========================================
2.6 Default use of XPath 1.0 as an Expression Language The XPath 1.0 specification [XPATH 1.0] defines the context in which an XPath expression is evaluated. When XPath 1.0 is used as an Expression Language in BPEL4People or inlined WS-HumanTask language elements then the XPath context is initialized as follows:
-- Context node: none
-- Context position: none
-- Context size: none
-- Variable bindings: all WS-BPEL variables visible to the enclosing element as defined by the WS-BPEL scope rules
-- Function library: Core XPath 1.0, WS-BPEL, BPEL4People and WS-HumanTask functions MUST be available and processor-specific functions MAY be available
-- Namespace declaration: all in-scope namespace declarations from the enclosing element
Note that XPath 1.0 explicitly requires that any element or attribute used in an XPath expression that does not have a namespace prefix must be treated as being namespace unqualified. As a result, even if there is a default namespace defined on the enclosing element, the default namespace will not be applied.
========================================
Kind Regards
Dieter König
Senior Technical Staff Member, WebSphere Process Server Architect IBM Software Group, Application and Integration Middleware Software WSS Business Process Solutions
Phone: +49-7031-16-3426 IBM Deutschland (Embedded
image moved
to file:
pic30086.gif)
E-Mail: dieterkoenig@de.ibm.com Schönaicher Str. 220
71032 Böblingen
Germany
IBM Deutschland
Research &
Development
GmbH /
Vorsitzender des
Aufsichtsrats:
Martin Jetter
Geschäftsführung:
Erich Baier
Sitz der
Gesellschaft:
Böblingen /
Registergericht:
Amtsgericht
Stuttgart, HRB
243294
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]