Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 38799 invoked by uid 500); 5 Jun 2003 11:08:53 -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 38786 invoked from network); 5 Jun 2003 11:08:53 -0000 Received: from smtp-gw.vdab.be (HELO MAIL.VDAB.BE) (193.53.240.93) by daedalus.apache.org with SMTP; 5 Jun 2003 11:08:53 -0000 Received: from MAIL.VDAB.BE ([193.53.240.218]) by MAIL.VDAB.BE (SAVSMTP 3.0.0.44) with SMTP id M2003060513083521084 for ; Thu, 05 Jun 2003 13:08:35 +0200 Received: from IGW-MTA by MAIL.VDAB.BE with Novell_GroupWise; Thu, 05 Jun 2003 13:08:34 +0200 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.2 Date: Thu, 05 Jun 2003 13:08:25 +0200 From: "Geert Van Damme" To: Subject: Re: commandline executes matching pipeline three times Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I've decided to use Cocoon as a webapp and run a batch job that calls the required URI, thus invoking Cocoon. The server needs to run anyway so this sounds like a fair solution. I'll take a look at the SourceWritingTransformer as it appears to do what I need. For now I wrote my own Transformer for the FTP transfer. Anyway thanks once again for all the help ! >>> uv@upaya.co.uk 06/05/03 10:23am >>> > thanks for the replies, it saves me a lot of frustration :) > In the application, a transformer will be used to transfer the > incoming XML to an FTP server. The resulting XML will contain info > about the transfer, such as size, failure/success, ... So it is > important that the transfer happens only once... If you have any other > suggestions for doing this, it would be appreciated ! Can you explain more exactly what you're trying to achieve? What transformer will you use? If you're talking about writing your own transformer, I would recommend using the SourceWritingTransformer and creating an FTPSource that you can write to. Even better, write a VFS source (giving other protocols too). The source itself could probably be configured to record success/failure, and to only transfer once. > (BTW, Cocoon2.1 is not an option at this point) It's a real shame that you're not able to use 2.1, as it now can write directly to modifiable sources. Therefore, if you had an FTP source, you could generate a page and have the CLI send it straight to your FTP server. > Thanks again ! You're welcome! Upayavira --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org For additional commands, e-mail: cocoon-users-help@xml.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org For additional commands, e-mail: cocoon-users-help@xml.apache.org