I known that it is a Microsoft problem, anyway I post the error to ask for a solution!
I develop a Web Service using JBossWS. The WSDL generated define some complex types... with inside some sequences....
When i use the WS with a Desktop client everything goes fine; instead the compact framework have some problem in recognize the sequence... in particular the order of fields into the various sequence did not follow the wsdl...!!!!!
I am also facing the similar problem. The generate file 'Reference.cs' doesnt get compiled as it gives compilation error ''System.Xml.Serialization.XmlElementAttribute' does not contain a definition for 'Form''
When I comment all the 'Form' in the file, it gets compiled but web service doesnt work. The server crips for out of sequence error.
Just wanted to know if this is resolved in .net compact framework 2.0 version.
We had the same issue in that the .NET compact framework does not handle unqualified too well.
Setting up a package-info.java with
@javax.xml.bind.annotation.XmlSchema(namespace = "http://a.c.f.i.com", elementFormDefault=javax.xml.bind.annotation.XmlNsForm.QUALIFIED) package a.c.f.i;
in the directory containing all the objects being transferred to the client solved it for us.
This is Microsofts Problem in CF.
Here the workaroundUse wsdl.exe /order to generate your client proxy class, and then remove all the code not supported by NetCF until your project compiles.Use Visual Studio to generate your client proxy class, then run wsdl.exe /order in some other directory, and copy just those lines of source code from the resulting class into your project source file that give the explicit ordering.