----- Original Message ----- From: "Glen Daniels" <[EMAIL PROTECTED]> To: "Axis-Dev (E-mail)" <[EMAIL PROTECTED]> Sent: Monday, October 07, 2002 20:49 Subject: Merge of i4 stuff
> We don't currently support <xsd:list> style enumerations. We should, I think, either 1) code up real support for this kind of thing, 2) throw errors when we encounter these constructs in WSDL, or 3) generate MessageElement/SOAPElement placeholders when we encounter them in WSDL. Comments about this in BeanDeserializer.onStartChild(). Once we resolve this, we should put the exception throwing code back in. yes, I've seen this with .net bitfield enums. you should know that when a .net bitfield enum contains an out of range value (its just an int), then the enum comes back as an int, rather than an enum string. so instead of "fun scary hard" you get "255". not tested to see if there is similar behaviour on classic enums; will give it a go soon.
