We test it for validation against a few small unit tests, but few people use it for more than smart code highlighting.
You might just want to hack up your local copy, as you noticed, its a nasty hairy beast. (Producing a schema at all was quite a chore. It made me want to take up carpentry or car repair or even cleaning up after circus elephants.) -Roger Roger Gonzalez mailto:[EMAIL PROTECTED] > -----Original Message----- > From: Spike [mailto:[EMAIL PROTECTED] > Sent: Saturday, March 05, 2005 4:25 PM > To: [email protected] > Subject: Re: [flexcoders] MXML Schema validation > > > Looks to me like the Schema is wrong. It doesn't allow for any > attributes of <mx:operation> and permits only the > <mx:request> tag as a > child. > > Anyone know if I can get my hands on on that's correct? > > Spike > > Spike wrote: > > Does anyone know whether the MXML Schema that comes with > Flex 1.5 really > > can be used for validation? > > > > Xerces is telling me that the <mx:operation> tag isn't > allowed to have a > > name attribute. The Flex documentation clearly states the > opposite is > > true and the tag would be pretty useless without it, so what is it > > that's going wrong? > > > > Xerces or the Schema? > > > > I've had a quick look at the schema myself, but my eyes > started to glaze > > over by the time I got to about line 5000. > > > > Spike > > > > -- > > -------------------------------------------- > Stephen Milligan > Code poet for hire > http://www.spike.org.uk > > Do you cfeclipse? http://cfeclipse.tigris.org > > > > Yahoo! Groups Links > > > > > > >
