[ODE-343] QName in xsi-type attribute value's prefix losing defining namespace declaration.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2
• Fix Version/s: 1.3.2
• Assignee: Matthieu Riou
• Reporter: Ciaran Jessup
• Created: 22/Jul/08 15:44
• Updated: 24/Apr/09 00:54
• Resolved: 24/Jul/08 18:40

Description

During BPEL Assign's in certain scenarios namespace prefix declarations which are required to maintain valid qnames in attribute values are dropped. This is a bit of a problem for me as it renders my XML documents invalid as they pass through ODE

I will attach a test process that exhibits the issue in due-course. If using SoapUI the following request should be valid:

<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:myns="myns">
<soapenv:Header/>
<soapenv:Body>
<myns:hello>
<myns:in xsi:type="myns:DustyMagicPixie">
<myns:value>Test message</myns:value>
<myns:dust>fooo</myns:dust>
</myns:in>
</myns:hello>
</soapenv:Body>
</soapenv:Envelope>

The response will have lost the prefix declaration for the namespace 'myns', but the xsi:type attribute on the myns:out element will still refer to this prefix, which will no longer map to any valid namespace . Currently I think the latest version of ODE also un-neccessarily redeclares the xsi namespace, which it never used to do before.

Issue Links

• relates to: ODE-402 OMUtils.toDOM could generate NPE if attribute value contains a colon