AFAIK this has been an issue for a long time, and the folks over at ms say it
is a design fault, and mark all the bug reports as false.
I posted a bug on connect for this over 6 months ago, but there hasn't been any
progress at all.
View the original post :
http://www.jboss.com/index.html?mo
Is it possible to disable validation of soap message ?
The Microsoft CF client generate an invalid order of fields in the sequence...
I would like to make no control over this message
I need some help plz!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=39
Since the parsing code relies on the order, the only solution you have is to
write a handler and then correct the order.
-Jason
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981176#3981176
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=po
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
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;
This is Microsofts Problem in CF.
Here the workaround
Use 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 othe
