[ https://issues.apache.org/jira/browse/ODE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou resolved ODE-343. ------------------------------- Resolution: Fixed Fix Version/s: 1.3 Assignee: Matthieu Riou Just fixed it on r679485. DOM is giving us a lot of pain on that one, basically there's no support for qualified attribute values, you have to do everything yourself. At least we have a testcase for it now: http://svn.apache.org/repos/asf/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestAttributeNamespaces/ > QName in xsi-type attribute value's prefix losing defining namespace > declaration. > --------------------------------------------------------------------------------- > > Key: ODE-343 > URL: https://issues.apache.org/jira/browse/ODE-343 > Project: ODE > Issue Type: Bug > Affects Versions: 1.2 > Reporter: Ciaran Jessup > Assignee: Matthieu Riou > Fix For: 1.3 > > Attachments: HelloWorld2.zip > > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.