
|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
SUBMITTED BY: Mark Ford
TARGET: HT, Section 6.2 Xpath Extension Functions
DESCRIPTION: It's not clear whether the functions require string literals
for the part, task, or LPG name params or whether callers can use
expressions for these values. In the ws-bpel 2.0 spec there are similar
instances where functions that accept the name of a resource (i.e.
bpel:getVariableProperty ) require that the name of the resource is passed
as a string literal. This is beneficial for static analysis and as well as
makes the behavior of the process/task easier to follow.
PROPOSAL: Add some text to the description of the Xpath extensions to
indicate that the part, task, and LPG params must be passed as string
literals. A similar change is required to the B4P spec. Formal proposal to
follow if the issue is opened.
|
|
Description
|
SUBMITTED BY: Mark Ford
TARGET: HT, Section 6.2 Xpath Extension Functions
DESCRIPTION: It's not clear whether the functions require string literals
for the part, task, or LPG name params or whether callers can use
expressions for these values. In the ws-bpel 2.0 spec there are similar
instances where functions that accept the name of a resource (i.e.
bpel:getVariableProperty ) require that the name of the resource is passed
as a string literal. This is beneficial for static analysis and as well as
makes the behavior of the process/task easier to follow.
PROPOSAL: Add some text to the description of the Xpath extensions to
indicate that the part, task, and LPG params must be passed as string
literals. A similar change is required to the B4P spec. Formal proposal to
follow if the issue is opened.
|
Show » |
|