Update: I filed a bug, and posted a fix. Shout out to Doug for his monkey patching info :)
http://bugs.adobe.com/jira/browse/SDK-15484 -J On Wed, May 7, 2008 at 11:37 AM, Josh McDonald <[EMAIL PROTECTED]> wrote: > Hi guys, > > I'm 99% sure I've located a bug in Flex's XML encoding for SOAP requests > that's mangling my <sequence maxOccurs="unbounded"> into a single element, > and I'd like to know who I need to talk to to help me fix it, so I can get > on with my work and submit a patch so everybody else can use it too. > > Please note that I'd really rather not go through the bugzilla process and > wait for Adobe to fix it. I'd have to spend 5 hours making a minimal failing > test case, stripping out all the business specific stuff, creating a custom > wsdl etc, and frankly I just don't have that much skill in XSDs etc. > > What I want to do if possible is email somebody who knows this part of > Flex and get their opinion on a couple of things, as I'm not 100% sure in > which step Flex is making the wrong decision. I've been stepping through > XMLEncoder and SOAPEncoder all morning, and it's a fairly deep stacktrace by > the time things go wrong, so I don't want to fix the wrong code. > > If anybody could point me in the right direction, it'd be much > appreciated! > > Cheers, > -J > > -- > "Therefore, send not to know For whom the bell tolls. It tolls for thee." > > :: Josh 'G-Funk' McDonald > :: 0437 221 380 :: [EMAIL PROTECTED] -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
