Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 58883 invoked from network); 14 Nov 2003 18:38:48 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 14 Nov 2003 18:38:48 -0000 Received: (qmail 20071 invoked by uid 500); 14 Nov 2003 18:38:30 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 20051 invoked by uid 500); 14 Nov 2003 18:38:30 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 20036 invoked from network); 14 Nov 2003 18:38:29 -0000 Received: from unknown (HELO mail.link77.net) (208.145.81.85) by daedalus.apache.org with SMTP; 14 Nov 2003 18:38:29 -0000 Received: from [172.20.3.18] (account lars_huttar@mail.jaars.org HELO LarsandKate) by mail.link77.net (CommuniGate Pro SMTP 4.1) with ESMTP-TLS id 29440654 for users@cocoon.apache.org; Fri, 14 Nov 2003 13:38:31 -0500 From: "Lars Huttar" To: "Cocoon Users List \(E-mail\)" Subject: Re: Writing to filesystem Date: Fri, 14 Nov 2003 12:38:26 -0600 Message-ID: <007e01c3aade$7ebd4260$120314ac@dallas.sil.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.6604 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 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 Hi all, The following was discussed back in July: > * From: Ali Mesbah > * Subject: Re: Writing to filesystem > * Date: Mon, 16 Jun 2003 05:54:12 -0700 > > As quoted from Geoff Howard <[EMAIL PROTECTED]>: > > It is complaining about the whitespace nodes between source:frament and > > title. > > You'll get this anytime you overwrite a whole document. To fix, just do > > something like: > > > > ... > > SourceWritingTransformer Test Result > > 1 > > ... > > Wonderful. Thanks it works :) > > > > At 08:39 AM 6/16/2003, you wrote: > > >As quoted from Upayavira <[EMAIL PROTECTED]>: > > >> > Hi, > > >> > > > >> > What is the best way to write the output of a Transformer (in a > > >> > pipeline) into a file (e.g. /resources/bla.xml) on the filesystem? > > >> > > >> Check out the SourceWritingTransformer. > > > > > >I am checking it out. thanks. I'm getting an error though: > > > > > >failedThere was a problem manipulating your document: > > >org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to > > >insert a node where it is not permitted. > > >writenonefile:/resources/result.xml > > > > > > > > >My xml source (called test.xml): > > > > > > > > > > > > context://resources/result.xml > > > > > > SourceWritingTransformer Test Result 1 > > > > > > > > > > > My problem is, the source fragment to be written out is a text string, generated using a series of and elements: -- SQL Server 2000 database schema for ... Even if I eliminate space between and , the same error still occurs. However if I wrap the text items in a dummy element: -- SQL Server 2000 database schema for ... the error goes away. Presumably it's complaining because the content of is just that, an XML fragment, rather than a proper XML document with one top-level node. But how can that be? Surely you can write text files using SourceWritingTransformer, not just XML documents. Besides, it used to work... I have a copy of the file from 10 days ago that was written out by this same pipeline. And I can't figure out what might have changed. Based on what Geoff said about overwriting, I tried deleting the old file first in case that helped. It didn't. Thanks for any hints, Lars --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org