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. Also, using system properties to configure the parser
may be a convenient solution but it can create more problems [1].
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.
I guess my disconnect is what is the point of having the ability to
specify a *parser* class using a system property if you can't also
configure the parser using system properties.
Maybe I'm just looking in the wrong place but I've spent all day trying
to find a clear and simple description of how to create a standalone
Xerxes-based SAX parser instance that can be used via the JAXP API and
will do schema validation (and also catalog-based schema component
resolution).
So far I have not been able to find that simple thing--all the docs I've
found are in the context of creating a parser and then using it
immediately in ones own code, not creating a parser class that will then
be used by JAXP parser users (e.g., Saxon).
Part of my frustration is that I know I only need to set a couple of
properties but I'm having a hard time figuring out how to do that in a
simple way.
Cheers,
Eliot
--
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 610.631.6770
www.reallysi.com
www.rsuitecms.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
