[
https://issues.apache.org/jira/browse/ODE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867325#action_12867325
]
Rafal Rusin commented on ODE-663:
---------------------------------
This still fails at 165 line.
ActivityType = OThrow
ActivityDeclarationId = 84
ScopeId = 25
ScopeDeclarationId = 10
ParentScopesNames = [__PROCESS_SCOPE:HelloXQueryWorld]
ScopeName = __PROCESS_SCOPE:HelloXQueryWorld
ProcessInstanceId = 22
ProcessId = {http://ode/bpel/unit-test}HelloXQueryWorld-1
ProcessName = {http://ode/bpel/unit-test}HelloXQueryWorld
Timestamp = Thu May 13 15:57:22 GMT-08:00 2010
LineNo = 165
Class = class org.apache.ode.bpel.evt.ActivityExecEndEvent
> DOMUtils.cloneNode results in invalid namespace declaration
> -----------------------------------------------------------
>
> Key: ODE-663
> URL: https://issues.apache.org/jira/browse/ODE-663
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.3, 1.3.4
> Reporter: Mark Ford
> Assignee: Rafal Rusin
> Priority: Critical
> Fix For: 1.3.4
>
> Attachments: ode1.x-663-v1.txt, ode1.x-663-v2.txt, ode1.x-663-v3.txt,
> ode1.x-663-v4.txt, ode1.x-663-v5.txt
>
>
> The DOMUtils.cloneNode code doesn't handle default namespace declarations
> correctly when processing an XQuery result from Saxon.
> For example:
> <ns1:parent xmlns:ns1="abc">
> <ns1:child xmlns="def">
> <ns2:nestedChild xmlns:ns2="def"/>
> </ns1:child>
> </ns1:parent>
> results in:
> <ns1:parent xmlns:ns1="abc">
> <ns1:child xmlns:xmlns="def">
> <ns2:nestedChild xmlns:ns2="def"/>
> </ns1:child>
> </ns1:parent>
> Notice that the default namespace has been rewritten as xmlns:xmlns which is
> invalid.
> Granted the above example is a bit odd, but strange things can happen when
> passing nodes in and out of XSLT and XQuery with respect to namespace
> declarations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
