Well, it seems like the problem is related to caching of schemas having same
namespaces.
I have two different schemas sharing the same namespace. I thought the
default behavior was not to cache schemas. I even tried to set caching to
false using cacheGrammarFromParse(false) and useCachedGrammarInParse(false)
but that's not helping.
Even resetCachedGrammarPool() doesn't help and only if I create a different
parser instance each time, the XML is validated successfully. Any ideas what
I might be doing wrong?

Thanks


-----Original Message-----
From: Alberto Massari [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 09, 2004 3:05 AM
To: [EMAIL PROTECTED]
Subject: Re: Importing namespaces


Hi,
maybe it's just a typo in the e-mail, but you have

>       <ocrq:request xmlns:ocrq="urn:or-request">

(note the "or" prefix), while the schema defines

>   xmlns:ocrq="urn:ocr-request"

(note the "ocr" prefix).

Alberto 



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


© 2004 OpenLink Financial 

Copyright in this message and any attachments remains with us.  It is
confidential and may be legally privileged.   If this message is not 
intended for you it must not be read, copied or used by you or 
disclosed to anyone else.   Please advise the sender immediately if 
you have received this message in error.

Although this message and any attachments are believed to be free of 
any virus or other defect that might affect any computer system into 
which it is received and opened, it is the responsibility of the 
recipient to ensure that it is virus free and no responsibility 
is accepted by Open Link Financial, Inc. for any loss or damage in any 
way arising from its use.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


© 2004 OpenLink Financial 

Copyright in this message and any attachments remains with us.  It is
confidential and may be legally privileged.   If this message is not 
intended for you it must not be read, copied or used by you or 
disclosed to anyone else.   Please advise the sender immediately if 
you have received this message in error.

Although this message and any attachments are believed to be free of 
any virus or other defect that might affect any computer system into 
which it is received and opened, it is the responsibility of the 
recipient to ensure that it is virus free and no responsibility 
is accepted by Open Link Financial, Inc. for any loss or damage in any 
way arising from its use.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to