I have an update on this. There is no problem with extending string unless there are more than one of the same element, I'm not sure if it's the unbounded max that causes it. I think that the hotfix 3 had something in it about this. I will have to explore that option.
--- In flexcoders@yahoogroups.com, Paul deCoursey <[EMAIL PROTECTED]> wrote: > > I have this issue when calling a WebService operation. If I have in the > schema an object that extends string the operation will fail and crash > teh browser. The idea is to send an object like this (represented in xml): > <collection uuid="1481091239084023r"> > <metadata name="Title">This is the title</meatadata> > ... > </collection> > > If I send the object with everything except the metadata it works fine. > If I add the metadata it fails. This works from other clients without > any issues. I have tried the flex hotfix 3, but that has other issues, > it fails to load imported schema references correctly. Has anyone had > experience with something like this? > > I am working on building a simple example that I can post that includes > the WSDL, the flex client that fails and a java war that provides the > soap service. Once I have that done I will post it, but I'd like to > know before hand if anyone has experienced this. Or if there is anyone > that has a complexType that extends string but does not fail, I'd be > interested in comparing notes there as well. > > Thanks > > Paul >
