DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26241>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26241 SAX features [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Additional Comments From [EMAIL PROTECTED] 2004-01-19 17:26 ------- Thanks Michael, specifying endorsed flag eliminate the SAXNotRecognizedException. But behavior became even more strange: it looks like SAX parser doesn't perform content type validation. When executed from WSAD it reports "Datatype errors", but executed from command line not anymore???? In both cases the same JDK (1.4.2_3)& same libraries (2.6.0) are used. In WSAD environment java.endorsed.dirs points to standard location ($JRE/lib/endorsed, that desn't exists in my environment). Pointing java.endorsed.dirs to proper location of the xerces jars results in the same behaviour in WSAD as well (no content validation performed). So now it consistent, at least :-) Validation flags used: "http://xml.org/xml/features/validation"; "http://apache.org/xml/features/validation/schema"; --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
