This class seems to do what I want given that I can't do what I want
from the command line.
But this seems like it would be a really common combination, namely
schema validation and catalog resolution but I couldn't find an example
of this combination anywhere. It would make really useful conv
[EMAIL PROTECTED] wrote:
>Hmm. I can see the point about properties affecting everything running
>under a single JVM in an app server but it still seems like there ought
>to be a convenient way to do this from the command line where the JVM
>instance is of course only going to apply to the on
>Hmm. I can see the point about properties affecting everything running
>under a single JVM in an app server but it still seems like there ought
>to be a convenient way to do this from the command line where the JVM
>instance is of course only going to apply to the one process being run.
If you're
Michael Glavassevich wrote:
So my questions are:
1. Is there a way to configure Xerces to do schema validation for
JAXP-based parser users from the command line?
There isn't and in general there's no way to accomplish that with Xerces
other features.
2. If not, why not?
No one asked for it
Hi Eliot,
Eliot Kimber <[EMAIL PROTECTED]> wrote on 03/10/2008 03:46:12 PM:
> I need to process schema-based documents with Saxon where the documents
> need to have default attribute values that are only in the schema (these
> happen to be DITA documents where the processing depends on the values
I need to process schema-based documents with Saxon where the documents
need to have default attribute values that are only in the schema (these
happen to be DITA documents where the processing depends on the values
of the common class= attribute which normally never exists in instances).
I'm
