Hi Loz, Thanks for your help, but I was actually able to do this what you're suggesting. The problems started when I tried to combine this with a solution to the main problem.
Alex > -----Original Message----- > From: Loz [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 13, 2002 3:38 AM > To: [EMAIL PROTECTED] > Subject: Re: DocumentBuilderFactory + grammar caching > > > Aleksandar Milanovic wrote: > > Hi All, > > > > > > An equally important question related to this is if I can > somehow instruct > > Xerces to: > > 1) ignore schemaLocation attribute > > 2) always take the schema from a schema cache > > Most of that went over my head. But for this bit, the schema document is > treated as an external entity (from the point of view of an instance > document to be validated). This means you could use a custom > EntityResolver with your DocumentBuilder to look the schema document up > on your database (and cache it). I think the EntityResolver will get > passed the schemaLocation attribute as the systemid. > > regards > > Loz > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
