Thank you. That's too bad! Why that, though? No time to implement those for Flex 3 or it was purposely ignored/not supported? All this waiting time for Flex3 to come out... was a waste. I really hoped Flex3 would address all the WebServices issues it has in its 2nd release.
--- In [email protected], "Todd" <[EMAIL PROTECTED]> wrote: > > In the DOcs for Flex 3 > http://livedocs.adobe.com/labs/flex3/html/help.html?content=data_access_\ 3.html > > At the end, there's the following sections: The following XML Schema > structures or structure attributes are ignored and are not supported > in Flex 3: > > <complexType > final="..." > block="..." > mixed="..." > abstract="..."/> > > Looks like abstract isn't supported. > > --- In [email protected], "Robert Csiki" emc_rcsiki@ wrote: > > > > > > In WSDL I have a complex type that contains an element type of an > > abstract type T1. Then I have the concrete complex type T2 that extends > > from T1. > > > > My WebService request contains an instance of T2 (which is also type of > > T1 as it extends from it). However, the SOAPEncoder ignores all its > > content and instead uses T1 (which is abstrace, it has nothing). > > SOAPEncoder.encodeRequest() results in a bad (incomplete) SOAP message > > => the Web Service request fails. > > > > Is this a known Flex Builder 3 bug? > > > > Thanks, Robert > > >
