ou?
Kevin
-Original Message-
From: Michael Ryan [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2003 3:41 PM
To: [EMAIL PROTECTED]
Subject: RE: Error in serialization of boolean fields
Yes, hand editing to use the correct namespace works just fine, but
unfortunately is not an adequate work-around
the build.
-Original Message-
From: Davis, Kevin [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2003 2:36 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Error in serialization of boolean fields
I know this may sound silly, but have you tried editing the generated
classes to
lto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2003 3:32 PM
To: [EMAIL PROTECTED]
Subject: FW: Error in serialization of boolean fields
I sent the following email some four months ago (twice), and got no
response. I recently downloaded the Axis 1.1 RC2 code, and tried again,
but the same
: Error in serialization of boolean fields
Hello all-
Just started using the released version 1.0 of Axis. I have
noticed that, for complex types, the generated classes are encoding
boolean fields as "soapenc:boolean" instead of as "xsd:boolean". The
fields are de
Hello all-
Just started using the released version 1.0 of Axis. I have
noticed that, for complex types, the generated classes are encoding
boolean fields as "soapenc:boolean" instead of as "xsd:boolean". The
fields are defined in the WSDL as "xsd:boolean", but the static field
description
Hello all-
Just started using the released version 1.0 of Axis. I have
noticed that, for complex types, the generated classes are encoding
boolean fields as "soapenc:boolean" instead of as "xsd:boolean". The
fields are defined in the WSDL as "xsd:boolean", but the static field
description
