Return-Path: Delivered-To: apmail-xml-general-archive@xml.apache.org Received: (qmail 78371 invoked by uid 500); 27 Jul 2001 02:08:55 -0000 Mailing-List: contact general-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: general@xml.apache.org Delivered-To: mailing list general@xml.apache.org Received: (qmail 78360 invoked from network); 27 Jul 2001 02:08:55 -0000 Message-ID: <3B60CD29.F001B52B@firstech.com> Date: Thu, 26 Jul 2001 19:08:41 -0700 From: Gary L Peskin Organization: The Firstech Corporation X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: general@xml.apache.org Subject: Re: xalan d7 build bug? was - Re: help - java - Basic DOM parse References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Scott, Don -- I think Rob is talking about a problem with the documentation at http://xml.apache.org/xalan-j/usagepatterns.html#plug It does state that all three files are in xalan.jar. Gary Scott_Boag@lotus.com wrote: > > > But when I look in the xalan.jar there is only: > > javax.xml.transform.TransformerFactory > > org.apache.xalan.processor.TransformerFactoryImpl > > I think I am confused as Edwin about your problem. > > I am guessing that you are expecting to see javax.xml.parsers.* stuff and > implementation in Xalan. These are implemented in Xerces, not Xalan. > Xalan only implements the javax.xml.transform.* part of JAXP 1.1. Please > see http://xml.apache.org/xerces-j/index.html. > > -scott > > > "Robert > Koberg" To: > om> Subject: xalan d7 build bug? was - Re: help - java - Basic DOM parse > > 07/26/2001 > 12:32 PM > Please > respond to > general > > > > I failed to mention I am using Xalan (D7). In the documentation (that says > D6 at the top) it states: > --------------------- > The Java API for XML Processing interfaces enable you to isolate your > application from the internal implementation details of a given > Transformer, > SAX parser, or DOM parser. For each of these objects, there is an abstract > Factory class with a static newInstance() method that instantiates a > concrete Factory which wraps the underlying implementation. These > newInstance() methods use system property settings to determine which > implementation to instantiate. > Xalan-Java is distributed with system property settings for the Xalan XSLT > Transformer and the Xerces DOM and SAX parsers. These settings are in > xalan.jar in META-INF/services (see src/META-INF/services). > System property Setting > javax.xml.transform.TransformerFactory > org.apache.xalan.processor.TransformerFactoryImpl > javax.xml.parsers.DocumentBuilderFactory > org.apache.xerces.jaxp.DocumentBuilderFactoryImpl > javax.xml.parsers.SAXParserFactory > org.apache.xerces.jaxp.SAXParserFactoryImpl > ------------------------------- > > But when I look in the xalan.jar there is only: > javax.xml.transform.TransformerFactory > org.apache.xalan.processor.TransformerFactoryImpl > > ----- Original Message ----- > From: "Robert Koberg" > To: > Sent: Thursday, July 26, 2001 9:14 AM > Subject: help - java - Basic DOM parse > > > I must be missing something very basic about DOM parsing. > > > > Here is an excerpt of the java code: > > > > DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance(); > > DocumentBuilder docbuilder = dfactory.newDocumentBuilder(); > > Document doc = docbuilder.parse(this_config); > > > > context.setAttribute("boo1", this_config); > > context.setAttribute("boo2", doc); > > > > The output indicates the correct file (with or without the file:///) if I > > check it in the filesystem, but doc is always null. dfactory, docbuilder > > all show that they have been created. The xml file is well-formed. > > > > thanks for any help, > > Rob --------------------------------------------------------------------- In case of troubles, e-mail: webmaster@xml.apache.org To unsubscribe, e-mail: general-unsubscribe@xml.apache.org For additional commands, e-mail: general-help@xml.apache.org