Martin, you definitely seem to have a valid point there. But recently another user reported a similar issue (through in the context of a UTF-16 encoded file), again just in the context of the XML schema reader, which is used internally by the XML code generator.
In other words, yes, I agree that the problem seems to be with the XML schema in question (as indicated by the error message) ... but let's be a bit careful. Regards Werner Martin S. Weber wrote: > Quoting "Hoebel, John" <[email protected]>: >> Parsing Error : Declared encoding "UTF-8" does not match actual one >> "Cp1252"; > > You claimed to use the UTF-8 encoding but really use the code page 1252 > windows encoding. How about you just save your schema as UTF-8 as you > claim to use that? > > I mean .. the error message is telling you everything, isn't it? > > (It's not even castor per se, but the xml parser trying to read your > schema which claims to be UTF-8 but isn't) > > -Martin > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
