WSDL first. Namespace of complx type's child elements.

Question

Hello!
I've got strange (for me) behavior of wscompile.
I started to develop a web service from a WSDL definition (document-literal). I built two services built on the written WSDL: one in Java (was deployed to JBoss) and one in .Net. Also I wrote a Java client that should be talking to either .Java or Net service.
The Java client communicates with .Net service properly. But doesn’t work with Java one. It fails to desterilise the structure.
My schema was defined with elementFormDefault="qualified", attributeFormDefault="unqualified". And there was a type that consists of some child elements. After comparing the SOAP messages from the services I payed attention that the Java service doesn’t define a namespace for child elements:
From .Net:
<?xml version="1.0" encoding="utf-8" ?>
<soap:Envelope
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<FindUserResponse xmlns="http://echo.test/types">
<User name="First" surname="Unknown"/>
<User name="Second" surname="Unknown"/>
</FindUserResponse>
</soap:Body>
</soap:Envelope>
From Java:
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:FindUserResponse xmlns:ns1="http://echo.test/types">
<User name="Mr.First" surname="Unknown"/>
<User name="Mr.Second" surname="Unknown"/>
</ns1:FindUserResponse>
</soapenv:Body>
</soapenv:Envelope>
So I think wscompile generates the server side type serialization wrongly - child elements of complex structure are unqualified. But the client code is generated properly.
When I defined in WSDL that the child elements of my complex type has an attribute: form="unqualified" and recompiled the services and the client, everything starts working.
Does somebody have any clue of the reason of such strange behaviour?
Thanks in advance.

Answer 1

I have the same problem.Jboss+Wscompile, and I in the Sopa response elements are not qualified. could you fix this issue? I need to use type substitution and I can not ahve unqualified as default.