Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 2834 invoked by uid 500); 1 May 2002 01:11:31 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 2822 invoked from network); 1 May 2002 01:11:31 -0000 From: "Vadim Gritsenko" To: Subject: RE: Changes to request parameters within an Action Date: Tue, 30 Apr 2002 21:11:18 -0400 Message-ID: <003601c1f0ad$1b111f80$9274558b@vgritsenkopc> 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, Build 10.0.2616 In-Reply-To: <200204302317.g3UNHsl5019215@mail.nmmn.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: Markus Braasch [mailto:mb@nmmn.com] > > Hello, > > What would be the best way to propagate changes to the request What kind of changes? > object from an Action back to a XSP page? I assume this was > attempted with the Cocoon DatabaseSelectAction, but it does > not appear to work since the method > > ObjectModelHelper.getRequest(objectModel) > > returns a copy of the request object, only. It's not a copy. > Would you suggest to access the request object directly through > the Java Servlet API? Request is no different from servlet API in most parts. Vadim > > Markus Braasch --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org