Return-Path: Delivered-To: apmail-xml-xerces-j-dev-archive@www.apache.org Received: (qmail 18509 invoked from network); 23 Nov 2003 19:32:13 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 23 Nov 2003 19:32:13 -0000 Received: (qmail 99952 invoked by uid 500); 23 Nov 2003 19:32:02 -0000 Delivered-To: apmail-xml-xerces-j-dev-archive@xml.apache.org Received: (qmail 99829 invoked by uid 500); 23 Nov 2003 19:32:01 -0000 Mailing-List: contact xerces-j-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: xerces-j-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list xerces-j-dev@xml.apache.org Received: (qmail 99813 invoked from network); 23 Nov 2003 19:32:01 -0000 Received: from unknown (HELO mail.speakeasy.net) (216.254.0.206) by daedalus.apache.org with SMTP; 23 Nov 2003 19:32:01 -0000 Received: (qmail 16007 invoked from network); 23 Nov 2003 19:32:05 -0000 Received: from unknown (HELO [192.168.254.4]) ([216.254.85.72]) (envelope-sender ) by mail.speakeasy.net (qmail-ldap-1.03) with RC4-SHA encrypted SMTP for ; 23 Nov 2003 19:32:05 -0000 Mime-Version: 1.0 X-Sender: elharo@mail.ibiblio.org Message-Id: In-Reply-To: <3FC0FF6A.4070702@apache.org> References: <3FBE48DF.92EBA572@ca.ibm.com> <3FBE8FB4.2080607@us.ibm.com> <3FBE9D73.3020900@apache.org> <3FBEC44E.3040200@us.ibm.com> <3FC0FF6A.4070702@apache.org> Date: Sun, 23 Nov 2003 14:05:50 -0500 To: xerces-j-dev@xml.apache.org From: Elliotte Rusty Harold Subject: Re: [ANNOUNCEMENT]: Xerces-J 2.6.0 now available Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N At 10:41 AM -0800 11/23/03, Andy Clark wrote: >I think you're being a little melodramatic, Elliotte. ;) > >As Michael stated, there is an easy mechanism to override >which parser configuration is used in Xerces by default. >And this would affect all Xerces instances in the JVM (or >custom class-loaded sandbox, if you want to use this >mechanism more than once in the same JVM), including the >parser instances created with JAXP. I have figured out how to do this. Thanks. However, I would not classify it as easy. It took several hours of wading through the Xerces source tree and experimentation to get it to work. Easy would be parser.setFeature("http://apache.org/xml/features/allow-XML1.1", false). A feature based solution would also make me feel more confident that this solution would continue to work in the future. Right now my code depends on about a dozen different protected and public methods in XNI, as well as suppositions about how, when, and why the XML11Configuration.parse(boolean complete) method is called, and which methods it should call in which order. I'm worried that some of this might change in the future in incompatible ways. I prefer working with pure SAX. Delving this deep into parser internals makes me very nervous. -- Elliotte Rusty Harold elharo@metalab.unc.edu Effective XML (Addison-Wesley, 2003) http://www.cafeconleche.org/books/effectivexml http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA --------------------------------------------------------------------- To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org For additional commands, e-mail: xerces-j-dev-help@xml.apache.org