"John Utz" <[EMAIL PROTECTED]> writes: > hacking the explicit path to the schema into personal-schema.xml solved > the problem. that's not surprising, it's a pretty typical problem and a > pretty typical hack. having this show up in Xerces-P is actually > *reassuring* :-) > > it might be appropriate to alter Schema.t to resolve the location of the > .xsd file instead of hacking the instance file because that way we avoid > making the instance file look different than the one shipped with the > other Xercen? Xercii? ( speak up all you latin speakers! :-) ).
I'm not sure why it's failing in your case. There's actually a bit of code in t/TestUtils.pm that is supposed to resolve the file path. In any case, I've decided to just switch to an entity resolver that supplies the files. jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
