It's a namespace issue, in the XSD either set elementFormDefault="qualified", or give the element names a prefix (and map that prefix to the namespace)
On 26 March 2012 16:03, Leandro de Oliveira <lehph...@gmail.com> wrote: > Hi, > > I don't understand why the following piece of XML is not valid to Xerces: > > <processor > xmlns="http://maven-config-processor-plugin.googlecode.com/schema/transformation"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > xsi:schemaLocation="http://maven-config-processor-plugin.googlecode.com/schema/transformation > http://maven-config-processor-plugin.appspot.com/schema/transformation-2.1.xsd";> > <add> > </add> > </processor> > > It's valid on http://validator.w3.org so is this a Xerces bug? Is > there any known workaround? I can change the schema file if necessary. > I'm using Eclipse Indigo to edit XML files. > > Thank you very much > > --------------------------------------------------------------------- > To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org > For additional commands, e-mail: j-users-h...@xerces.apache.org > -- Andrew Welch http://andrewjwelch.com --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org
