Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 62971 invoked by uid 500); 4 Dec 2002 15:10:13 -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 62960 invoked from network); 4 Dec 2002 15:10:12 -0000 Message-ID: <5C9461BDD6ABD511815500D0B7B7A0E203503872@nt_2.asset-internal> From: =?iso-8859-2?Q?=CFURDINA_Michal?= To: "'cocoon-users@xml.apache.org'" Subject: DOMStreamer doesn't work with Saxon Date: Wed, 4 Dec 2002 16:11:25 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-2" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello! I have a problem when using Saxon as my only TRAX Transformer. In XSP page I have the following: myLogicsheet: org.w3c.dom.Element getElement() {...} myXSPPage: myLogicSheet.myClass.getElement() This construction creates XML with element returned by logicsheet function i.e. . When using Xalan as my XSLT Transformer, this construction works. But NO element is created when using Saxon. Can anyone tell me, what's going on? (the problem must be somewhere in XSPObjectHelper or in DOMStreamer). Mike. PS: I am using Tomcat 4.1.12, Cocoon 2.0.3 and Saxon 6.5.2. PS2: Our logicsheets were created for Cocoon 1.8, and returns DOM objects, but they should be working because of DOM->SAX wrapping in XSP we depend on. Too much work to rewrite it. -- MisoD -- Michal Durdina - durdina@asset.sk ASSET Soft a.s., Kosicka 56, Bratislava, 821 08 Slovakia, Europe --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: