ID processing seems to work OK these days without dynamic validation being
turned on, so I simply commented out the setting of dynamic validation for
the source tree (I should do it for the stylesheet also, but, one thing at
a time). Please give it another try.
-scott
Scott Boag
To: [EMAIL PROTECTED]
06/20/2001 cc: [EMAIL PROTECTED]
09:17 AM Subject: Re: Antwort: Re: Antwort: [Bug
2124] - Status of SAXSource
is changed in Xalan 2.1.0(Document link:
Scott Boag)
Thomas, I am getting more and more confused by this.
Dynamic validation has, in fact, been turned on for a long time, correct?
The only thing that is different in the recent code is that errors are
being properly reported, correct?
-scott
Scott Boag
To: [EMAIL PROTECTED]
06/20/2001 cc:
08:42 AM Subject: Re: Antwort: Re: Antwort: [Bug
2124] - Status of SAXSource
is changed in Xalan 2.1.0(Document link:
Scott Boag)
> If XSLT 2.0 becomes W3C Recommendation (or working draft) then it
> contingently makes sens to use dynamic validation as default because you
> need it to use the XMLSchema.
The id(...) function won't work correctly with validation turned off now,
correct?
-scott
Thomas2.Maesing
@bgs-ag.de To: [EMAIL PROTECTED]
cc: (bcc: Scott Boag/CAM/Lotus)
06/20/2001 Subject: Antwort: Re: Antwort: [Bug
2124] - Status of SAXSource is
04:00 AM changed in Xalan 2.1.0
Please respond
to xalan-dev
Yes,
I think so because it is the default behavior from xalan-j 1(in a later
version it was switched on, but as specified in the documentation of itself
it
should not. But this was no problem because errors did not stop the
transformation) up to xalan-j_2_1_0. It is also the default
behavior of Saxon.
I have found nothing in the XSLT Spec that a XSLT Processor should be a
validating XMLProcessor for the Source Document.
I also have found nothing in JAXP 1.1 Spec regarding to the transform
package.
So in my opinion at the time it should not be used as default.
If XSLT 2.0 becomes W3C Recommendation (or working draft) then it
contingently makes sens to use dynamic validation as default because you
need it to use the XMLSchema.
Regards
Thomas
[EMAIL PROTECTED] am 19.06.2001 19:18:36
Bitte antworten an [EMAIL PROTECTED]
An: [EMAIL PROTECTED]
Kopie:
Thema: Re: Antwort: [Bug 2124] - Status of SAXSource is changed in Xalan
2.1.0
Hi Thomas. I just want to be clear. You are proposing to turn off dynamic
validation altogether?
> Another possible way is to provide the direct validation/dynamic feature
> to the user
> as Attribute (via setAttribute(java.lang.String name, java.lang.Object
> value)) .
No. I don't want to get into the business of setting properties on the
XMLReader... that's what SAXSource is there for.
I think dynamic validation is the right default, but I understand your
problem. I really think this is a sort of Parser bug, but that's only my
opinion, and doesn't help much right now. I'll look into it a bit further.
-scott
