Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 51501 invoked by uid 500); 13 Feb 2002 17:50:31 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 51444 invoked from network); 13 Feb 2002 17:50:31 -0000 From: "SANSONE, AARON M [Non-Pharmacia/1000]" To: "'cocoon-users@xml.apache.org'" Message-ID: <6A1BB598448ED31198DC0008C75B715309A4910B@ems1000-05.monsanto.com> Subject: RE: More on Cocoon 2 generated SAX Exception Date: Wed, 13 Feb 2002 11:49:53 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N More info: RE: SAX to DOM Pipeline with an AbstractDOMTransformer In an attempt to determine what was causing this exception, I dug into the code and started to low-tech debug (aka System.out.println). I found something interesting. The content handler is NULL when trying to process the SAX Events through the AbstractDOMTransformer. I added a series of printlns in the AbstractXMLPipe on start and end document and the start and end element methods. In each case the contentHandler is NULL. Hopefully this will help in debugging. -Aaron -----Original Message----- From: SANSONE, AARON M [Non-Pharmacia/1000] Sent: Tuesday, February 12, 2002 10:30 AM To: 'cocoon-users@xml.apache.org' Subject: RE: More on Cocoon 2 generated SAX Exception Per Vadim's suggession, I've upgraded to Cocoon 2.0.1. However I am still having a problem with this pipeline. Here is the error now: DEBUG (2002-02-12) 10:21.36:390 [core] (/showTree) web-5/SQLTransformer: RECEIVED CHARACTERS: FATAL_E (2002-02-12) 10:21.36:450 [core.xslt-processor] (/showTree) web-5/TraxErrorHandler: Error in TraxTransformer: javax.xml.transform.TransformerException: java.lang.NullPointerException javax.xml.transform.TransformerException: java.lang.NullPointerException at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j ava:1230) at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:3139) at java.lang.Thread.run(Thread.java:484) --------- java.lang.NullPointerException at org.apache.cocoon.xml.dom.DOMBuilder.getDocument(DOMBuilder.java:119) at org.apache.cocoon.xml.dom.DOMBuilder.notifyListener(DOMBuilder.java:144) at org.apache.cocoon.xml.dom.DOMBuilder.endDocument(DOMBuilder.java:136) at org.apache.xalan.transformer.ResultTreeHandler.endDocument(ResultTreeHandler .java:190) at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j ava:1186) at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:3139) at java.lang.Thread.run(Thread.java:484) DEBUG (2002-02-12) 10:21.36:460 [core] (/showTree) web-5/LogKitLogger: Returning a org.apache.cocoon.components.sax.XMLByteStreamInterpreter to the pool Please reference the original email for the sitemap and transformer code. Thanks, Aaron -----Original Message----- From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net] Sent: Monday, February 11, 2002 5:41 PM To: cocoon-users@xml.apache.org Subject: RE: More on Cocoon 2 generated SAX Exception > From: SANSONE, AARON M [Non-Pharmacia/1000] > > Cocoon 2.0 - Running on P3-500 NT 4.0 SP6 with JRun 3.1 > > Here is some extra exception information from root.log I didn't include > before: > > org.xml.sax.SAXException: Invalid state > at > org.apache.cocoon.xml.dom.DOMBuilder.characters(DOMBuilder.java:462) > at This class was refactored in Cocoon 2.0.1. Can you upgrade to 2.0.1? It might not have the issue you are describing. Vadim --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: