Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 56183 invoked by uid 500); 17 May 2001 17:03:54 -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 55793 invoked from network); 17 May 2001 17:03:48 -0000 Date: Thu, 17 May 2001 13:03:47 -0400 (EDT) From: Jason Foster To: cocoon-users@xml.apache.org Subject: Re: XSP and sitemap objectModel In-Reply-To: <990110774.3b03e436bb76d@mail.otego.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N One thing that's clear to me is that I'm pretty confised about all of the various places that a component can hide information. If you could comment on or add to the following summary that would be great! Place Purpose --------------------------------------------------------------------- Request parameters --> hold form info from client Request attributes --> ??? Session attributes --> hold persistent client info Action/Matcher objectModel --> allow flow control Action parameters --> ??? The param available to a Selector --> ??? You mentioned "sitemap parameter elements" but I'm not entirely sure what you mean by that. I think that you are referring to both the Action parameters and the param available to a selector. I think I'm most confused by the difference between an Action parameter and an Action objectModel. This all came from my desire to pass information from an Action to an XSP page. For example if I have an action that adds "previous-result=fail" to its objectMap, how can my XSP page read from that to find out what to extract from the database? I get the impression that I could use a selector to accomplish some of this but somehow that doesn't feel right. What I wouldn't give for some sitemap design heuristics! > You are mistaken :) the discussion is if Matchers and Selector should have > access to sitemap parameter elements. OK, so to me a valid question is whether or not an XSP page should also have access to the sitemap parameters. Conversely shouldn't everything have access to the environment? If this isn't that case then it's pretty difficult for actions to control things, isn't it? Something like the following looks pretty straightforward: Thanks again for taking the time to help me out! Jason Foster --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: