Invalid XML Response - missing xmlns=''

Question

I have a simple BPEL WebService using a xsd elementFormDefault="unqualified".
{color:#0000ff}+<schema attributeFormDefault="unqualified"+
elementFormDefault="unqualified"
targetNamespace="http://xmlns.oracle.com/InvalidXMLResponse"
xmlns="http://www.w3.org/2001/XMLSchema">
+<element name="InvalidXMLResponseProcessRequest">+
+<complexType>+
+<sequence>+
+<element name="input" type="string"/>+
+</sequence>+
+</complexType>+
+</element>+
+<element name="InvalidXMLResponseProcessResponse">+
+<complexType>+
+<sequence>+
+<element name="result" type="string"/>+
+</sequence>+
+</complexType>+
+</element>+
+</schema>+{color}
I invoke this WebService with the Web Service Test Page of OC4J
and get an invalid xml-response (missing xmlns="").
If i look inside the bpel-console in the instance-flow at the reply activity the
xml-response looks good.
GOOD Reponse (at bpel-console):
+<InvalidXMLResponseProcessResponse xmlns="http://xmlns.oracle.com/InvalidXMLResponse">+
+<result {color:#ff0000}*xmlns=""*{color}>test</result>+
+</InvalidXMLResponseProcessResponse>+
Invalid Response (at every WS Client):
+<InvalidXMLResponseProcessResponse xmlns="http://xmlns.oracle.com/InvalidXMLResponse">+
+<result>test</result>+
+</InvalidXMLResponseProcessResponse>+
It seams that the xml serializer of the oc4j container does create a valid xml-response.

Answer 1

I just retested the testcase with an other test environment (10.1.3.4 MLR#3) and everything worked fine.
{color:#0000ff}+<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">+
+<env:Header/>+
+<env:Body>+
+<InvalidXMLResponseProcessResponse xmlns="http://xmlns.oracle.com/InvalidXMLResponse">+
+<result xmlns="">test</result>+
+</InvalidXMLResponseProcessResponse>+
+</env:Body>+
+</env:Envelope>+{color}
So there should be an availagle bugfix for this issue.
I need this bugfix for 10.1.3.3.1 because this is our production environment.