WebService serialization fails

Question

Hi,
I'm not sure if this is a bug or a compatibility issue...
When I compile the same code in Flex 3 to call a web service
as I used in Flex 2, the web message (viewed in Fiddler) includes
namespace definitions on each node in the header which are not
there in Flex 2. (Example below)
This means that when the message hits the server it won't
deserialize.
Using Fiddler I can remove the namespaces and resubmit the
request and it works.
Is there some new functionality in the Flex 3 SDK to specify
whether the namespaces should appear or is it a bug?
eg:
Flex 2:
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Header><AuthHeader><BrowserType>test< /BrowserType><Password>test</Password><Logon>test</Logon><MovieVersion>test</MovieVersion> <ScreenSize>test</ScreenSize></AuthHeader></SOAP-ENV:Header><SOAP-ENV:Body><Login
xmlns="
http://eCRF.ServiceContracts"
/></SOAP-ENV:Body></SOAP-ENV:Envelope>
Flex 3:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:s="
http://www.w3.org/2001/XMLSchema"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Header>
<AuthHeader>
<tns:Logon xmlns:tns="
http://eCRF.ServiceContracts">test</tns:Logon>
<tns:Password xmlns:tns="
http://eCRF.ServiceContracts">test</tns:Password>
<tns:ScreenSize xmlns:tns="
http://eCRF.ServiceContracts">test</tns:ScreenSize>
<tns:BrowserType xmlns:tns="
http://eCRF.ServiceContracts">test</tns:BrowserType>
<tns:MovieVersion xmlns:tns="
http://eCRF.ServiceContracts">test</tns:MovieVersion>
</AuthHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<tns:Login xmlns:tns="
http://eCRF.ServiceContracts"/>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Thanks
Dom

Answer 1

Further , These are the complete requirements for complex type object---->
J2SE SDK Classes
JAX-RPC supports the following J2SE SDK classes:
java.lang.Boolean
java.lang.Byte
java.lang.Double
java.lang.Float
java.lang.Integer
java.lang.Long
java.lang.Short
java.lang.String
java.math.BigDecimal
java.math.BigInteger
java.net.URI
java.util.Calendar
java.util.Date
Primitives
JAX-RPC supports the following primitive types of the Java programming language:
boolean
byte
double
float
int
long
short
Arrays
JAX-RPC also supports arrays that have members of supported JAX-RPC types. Examples of supported arrays are int[] and String[]. Multidimensional arrays, such as BigDecimal[][], are also supported.
<b>Value Types
A value type is a class whose state can be passed between a client and a remote service as a method parameter or return value. For example, in an application for a university library, a client might call a remote procedure with a value type parameter named Book, a class that contains the fields Title, Author, and Publisher.
To be supported by JAX-RPC, a value type must conform to the following rules:
It must have a public default constructor.
It must not implement (either directly or indirectly) the java.rmi.Remote interface.
Its fields must be supported JAX-RPC types.
The value type can contain public, private, or protected fields. The field of a value type must meet these requirements:
A public field cannot be final or transient.
A nonpublic field must have corresponding getter and setter methods</b>
Hope this helps.
Regards,
Piyush