We're not having any problems. Xerces2 is backwards compatable. We're
upgrading for the Parser Configuration and Grammar caching. The only
difference has been that the Xerces.jar file has been split into 2-3 jar
files.
Good luck with it!
From: Rufoo <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTE
Try using a Parser Configuration and register a error handler with it.
From: "Shital Joshi" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: schema validation using xerces sax parser
Date: Tue, 22 Apr 2003 10:11:03 -0400
Hi there,
I am trying to validate a 20MB XML
Yep, works for me too. THANK YOU!
From: "Constantine Georges" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: Caching Schemas
Date: Mon, 21 Apr 2003 17:52:00 -0400
Hi Jeff,
Thanks!
That did the trick.
C
To:
something from its corresponding
namespace. For example, , xsi:schemaLocation, etc. But certainly
not .
Hope this helps,
Sandy Gao
Software Developer, IBM Canada
(1-905) 413-3255
[EMAIL PROTECTED]
"Glenn Barnard"
<[EMAIL PROTECTED]To:
using the API improperly? It
doesn't seem that way to me, but you never know...
Thanks,
C
To:
[EMAIL PROTECTED]
"Glenn Barnard" cc: (bcc: Constantine
Georges/Towers Perrin)
you have to). When the parser
asks for S (by calling your entity resolver), you return an InputSource
with a Reader or InputStream in it for S.
Note that this has nothing to do with caching schemas.
Cheers,
Sandy Gao
Software Developer, IBM Canada
(1-905) 413-3255
[EMAIL PROTECT
will add to
the report with "here's my problem, too" stuff.
C
To:
[EMAIL PROTECTED]
"Glenn Barnard" cc: (bcc: Constantine
Georges/Towers Perrin)
This feature works well when schemas and sub-schemas are on disk. However,
our application calls for loading schemas and sub-schemas from an XML/RPC
server, meaning that the schemas reach the client as text.
In my initial test, I have a master schema and one sub-schema. If I load the
master (to
