Hi Dave,
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 2005. janu�r 7. 21:57
> To: [email protected]
> Subject: Re: FW: Command line parameters patch + XSD validation question
>
> > Hi All,
> >
> > Anyone cares to comment on my previous message (attached below)? I
> > haven't received any replies since I've sent it...
>
> The patches for handling schema files from the command line would be
> great. If you could create a Jira report, and attach the patches, that
> would be great.
As soon as I get some pointers on how to do that... (Sorry, I'm still new to
this list.) What information do I need to acces Jira? Where do I access it?
> The change for the document() is more problematic, because it changes
> long-standing behavior, which we cannot really do. It would be nice to
> have switches for the various recover options that XSLT allows for these
> sorts of errors, but that's a much more complicated thing.
Yes, I thought that this solution would not be correct this way. I think the
correct solution would be to add a command line switch (which I have done), and
based on the value of that switch rethrow a fatal error exception in the
document function handler.
My two problems are:
1. I got as far as setting this switch in the DOM parser
(theParser->setValidationConstraintFatal () in
xalanc/XercesParserLiaison/XercesParserLiaison:
XercesParserLiaison::CreateDOMParser())
but I don't know how I can access this setting from the document function
handler in
xalanc/Xslt/FunctionDocument.cpp:parseDoc()
2. What will be the exception type for a fatal error during parsing? (Which
exception do I need to rethrow?)
I think this solution should be acceptable as it doesn't break the
long-standing behaviour since it changes exception handling only based on the
value of the command line switch.
TIA:
Andras Babos.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
