namespaces feature

Hi, According to http://www.megginson.com/SAX/Java/namespaces.html, namespaces and namespace-prefixes can't be false together. Xerces allows both the features to set to false together. Any comments. Cheers, Rahul. Sun Microsystems, Inc. -

DO NOT REPLY [Bug 4456] - Not all correct encoding is supported

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 3493] - 17 Failures in Xerces2[beta2] aganist Domunit Test Suites.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Sax feature should throw SAXNotSupportedException.

> Right now, we can set feature > http://xml.org/sax/features/external-general-entities to true even if we have > http://xml.org/sax/features/validation to false. It should throw the > SAXNotSupportedException as per SAX specification. You are misreading the specification. It simply states tha

Sax feature should throw SAXNotSupportedException.

Hi According to latest SAX doc from http://www.saxproject.org/apidoc/org/xml/sax/package-summary.html, when external-general-entities and external-parameter-entities should be always true when validation feature is true. If the application attempts to set a feature state or property v

Re: patch for AbstractSAXParser

> I feel letting the parser throw an NPE is not a good idea. That is not consistent with Java programming practice. In particular, when the problem is that a null pointer is found when one is not allowed you are supposed to throw a NullPointerException. Even in the official SAX distribution, o

Re: patch for AbstractSAXParser

Glenn wrote : > Pavani writes: > > >Please find the attached patch for AbstractSAXParser. > >parse(inputSource) throws a NullPointerException if 'inputSource' is null. > > > +if (inputSource == null) { > > +throw new SAXException("InputSource is null"); > > +} > > T

Re: patch for AbstractSAXParser

Pavani writes: >Please find the attached patch for AbstractSAXParser. >parse(inputSource) throws a NullPointerException if 'inputSource' is null. > +if (inputSource == null) { > +throw new SAXException("InputSource is null"); > +} This seems like an unusual change t

patch for AbstractSAXParser

Hi, Please find the attached patch for AbstractSAXParser. parse(inputSource) throws a NullPointerException if 'inputSource' is null. Thanks, Pavani -- Pavani Mukthipudi Sun Microsystems Inc. Phone: 080 - 2298989 Extn: 87390 Index: AbstractSAXParser.java

DO NOT REPLY [Bug 3503] - setIgnoringComments does not seem to work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 4769] - DomBuilderFactory's setIgnoringComment(boolean) does not work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 5298] - Bug in parsing xml decl when it has white spaces preceding it in the document

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu