Hi Michael,
The example I posted is just an example of the structure of the document..
The real documents contain schemaLocation attributes so they can be resolved
by an entity resolver..
Anyway.. I tried your example of an EntityResolver-free handler. Setting the
schema locations this way is a
Hi Jo,
Your example doesn't contain any schemaLocation attributes. If your
document really looks like that I wouldn't expect your EntityResolver [1]
to be called. There's no schema location to report to it. If you were
expecting to resolve the schema documents based on their target namespace
y
/Jo Vandermeeren/:
I want to parse and validate the entire message in 1 run, and need to
use 2 XSD schemas.
The XSD's used for validation are packaged inside our application and
need to be resolved locally.. I can attach an EntityResolver on the
parser, but
only one call is issued to resolve t
don't see it by tomorrow.
- Rick
*** Sent via BlackBerry
-Original Message-
From: Jo Vandermeeren <[EMAIL PROTECTED]>
To: j-users@xerces.apache.org
Sent: Mon Jan 29 05:07:19 2007
Subject: Re: Resolving multiple XSDs/namespaces
Rick,
Thanks for your response.
Both sc
ation.
- Rick
*** Sent via BlackBerry
-Original Message-
From: Jo Vandermeeren <[EMAIL PROTECTED]>
To: j-users@xerces.apache.org
Sent: Mon Jan 29 01:21:29 2007
Subject: Resolving multiple XSDs/namespaces
Hi fellow xerces users,
The project I'm working on uses XML as transpo
:21:29 2007
Subject: Resolving multiple XSDs/namespaces
Hi fellow xerces users,
The project I'm working on uses XML as transport wrapper for data, much like a
SOAP wrapper that contains XML content.
I want to parse and validate the entire message in 1 run, and need to use 2 XSD
schemas.
Th
Hi fellow xerces users,
The project I'm working on uses XML as transport wrapper for data, much like
a SOAP wrapper that contains XML content.
I want to parse and validate the entire message in 1 run, and need to use 2
XSD schemas.
The XSD's used for validation are packaged inside our application
