Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 93629 invoked from network); 10 Nov 2003 02:29:33 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 10 Nov 2003 02:29:33 -0000 Received: (qmail 10961 invoked by uid 500); 10 Nov 2003 02:28:52 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 10809 invoked by uid 500); 10 Nov 2003 02:28:50 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 10715 invoked from network); 10 Nov 2003 02:28:50 -0000 Received: from unknown (HELO scaup.mail.pas.earthlink.net) (207.217.120.49) by daedalus.apache.org with SMTP; 10 Nov 2003 02:28:50 -0000 Received: from 1cust200.tnt3.barrie.on.da.uu.net ([66.48.153.200] helo=andrzej) by scaup.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1AJ1nW-00073N-00; Sun, 09 Nov 2003 18:28:59 -0800 From: "Andrzej Jan Taramina" Organization: Chaeron Corporation To: users@cocoon.apache.org Date: Sun, 09 Nov 2003 21:29:15 -0500 MIME-Version: 1.0 Subject: Best way to edit XML file using Cocoon? Reply-to: andrzej@chaeron.com CC: dev@cocoon.apache.org Message-ID: <3FAEB1AB.12161.6166C0@localhost> Priority: normal X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body 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 I'm writing an application that presents a high level UI to the users in a browser, but under the covers it is building/editing/modifying an XML document which keeps track of all the things the user wants to do. Any advice on the best way to implement this? I figured on storing a DOM instance in the users session, and then using flowscript to control the app flow and to edit the XML DOM structure in the session as each user request comes in. When the user has completed the workflow, I would serialize the DOM instance out into a database for storage. Thoughts? Suggestions? Thx! Andrzej Jan Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com