Hi Thomas,
I'd recommend you change the service so that is uses fully qualified
element names. This would fix the issue you're having with empty data
coming back.
When you use the unqualified form, all elements are placed into the
non-namespace. While it is a valid thing to do from an XML perspective,
what it does is make for interop problems. The default form is "qualified"
- so if you just make your XML qualified (e.g. includes the use of
namespaces) you get full compatibility on the compact framework.
The compact framework is not an exact port of the .NET framework. You can
use the following link to get the docs that let you complare, class by
class.
http://msdn.microsoft.com/library/en...parisonswithne
tframework.asp
For the XmlElementAttribute class, the Form property only exists on the
full class library implementation.
I hope this helps
Dan Rogers
Microsoft Corporation
--------------------
Thread-Topic: WSDL problem with .Net mobile
thread-index: AcToHDqalsHFgIFwTZiVyODuNT+JNw==
X-WBNR-Posting-Host: 212.144.115.118
From: =?Utf-8?B?VGhvbWFz?= <Th****@discussions.microsoft.com>
Subject: WSDL problem with .Net mobile
Date: Wed, 22 Dec 2004 03:49:01 -0800
Lines: 29
Message-ID: <07**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices:8261
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
Hi,
I have written a Web Service using Axis C++ Server and a .Net Windows
client. I considered every interoperability issue between Axis and .Net(
Doc/Literal ...)
The .Net Windows client can communicate with Axis without any problems. Now
I want to use my Web Service on a windows CE pocket pc but the problem is
that .Net don't create a client stub that can be compiled. If I try to
compile in .Net the following errors occur:
System.Xml.Serialization.XmlElementAttribute has no definition for 'Form'
This error never occured in my Windows Application. Could it be that .Net
Mobile use a thinner Web Services library?
The wsdl generated client stub:
--------------------------
[System.Xml.Serialization.XmlTypeAttribute(Namespac e="urn:Foo")]
public class transmission {
/// <remarks/>
/**************** .Net has problems with this declaration
******************/
[System.Xml.Serialization.XmlElementAttribute(Form= System.Xml.Schema.XmlSche
maForm.Unqualified, IsNullable=true)]
public string String_1;
}
I tried to delete the phrase with Form=System.Xml... and the now .Net
compiled my Client but the fields in a Structure were NULL.
