Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 44614 invoked by uid 500); 17 Sep 2002 02:30:17 -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 44602 invoked from network); 17 Sep 2002 02:30:16 -0000 From: "Per Kreipke" To: Subject: RE: Dynamic XML Content to Generator Date: Mon, 16 Sep 2002 22:34:02 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <9622F162-C9B3-11D6-B8D7-00039310453C@mac.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Why not generate XML in an Action? If not, how would you pass the > business data generated from an Action to a Generator? What I did was > create a Generator that took as its source the XML document and that > worked fine. In this manner, the Action was used as a business > delegate, obtaining information from a variety of sources and composing > it into an XML document which I passed to a generator that accepted XML > documents versus files to XML documents. Using the ServerPagesAction allows you do this very easily and cleanly. Its default behavior is to return 'success' from any existing XSP and put the generated content in a request attribute of your choosing. From there, it can be gotten from your generator (I personally then end up using it back in XSP again). Per --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: