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

Karthick Sankarachary commented on ODE-664:
-------------------------------------------

Maybe we're talking about different things here. Can you indicate the violation 
in the RE strategy that is described below?

RE (Replace-Element-properties):

o       Replace the element at the destination with a copy of the entire 
element at the source, including [children] and [attribute] properties.

An optional keepSrcElementName attribute is provided to further refine the 
behavior. [SA00042] It is only applicable when the results of both from-spec 
and to-spec are EIIs, and MUST NOT be explicitly set in other cases. A WS-BPEL 
processor MAY enforce this checking through static analysis of the 
expression/query language. If a violation is detected during runtime, a 
bpel:selectionFailure fault MUST be thrown.

§         When the keepSrcElementName attribute is set to "no", the name (i.e. 
[namespace name] and [local name] properties) of the original destination 
element is used as the name of the resulting element. This is the default value.

§         When the keepSrcElementName attribute is set to "yes", the source 
element name is used as the name of the resulting destination element.

When the keepSrcElementName attribute is set to "yes" and the destination 
element is the Document EII of an element-based variable or an element-based 
part of a WSDL message-type-based variable, a WS-BPEL processor MUST make sure 
the name of the source element belongs to the substitutionGroup of the 
destination element used in the element variable declaration or WSDL part 
definition. The substitutionGroup relation is determined by XML Schemas known 
to the WS-BPEL processor. [SA00094] A WS-BPEL processor MAY enforce this 
checking through static analysis of the expression/query language. If a 
violation is detected during runtime, a bpel:mismatchedAssignmentFailure fault 
MUST be thrown.

> Namespace declarations not being copied in ASSIGN.replaceElement
> ----------------------------------------------------------------
>
>                 Key: ODE-664
>                 URL: https://issues.apache.org/jira/browse/ODE-664
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.3.3, 1.3.4
>            Reporter: Mark Ford
>            Assignee: Karthick Sankarachary
>            Priority: Critical
>
> The following line in ASSIGN.replaceElement looks wrong:
>         DOMUtils.copyNSContext(ptr, replacement); 
> I think it should be:
>         DOMUtils.copyNSContext(src, replacement); 
> The rationale is that the RE strategy should copy the attributes from the 
> source element to the target element. Without this change, you may end up 
> with undeclared namespace prefixes in the output of your BPEL.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to