Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 29009 invoked by uid 500); 5 Nov 2001 13:57:30 -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 28997 invoked from network); 5 Nov 2001 13:57:29 -0000 Date: Mon, 5 Nov 2001 14:56:51 +0100 (CET) From: giacomo X-X-Sender: To: Subject: RE: Cocoon-view, Cocoon-sitemap documentation In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, 5 Nov 2001, Torsten Curdt wrote: > > > I was trying to use to "?cocoon-view=view" query-parameter > > > on serveral URL. > > > > > > Sadly for the http://localhost:8080/cocoon/documents/* URLs > > > Cocoon always responded with an HTML content. > > > > > > As I was digging around in > > > \org\apache\cocoon\components\language\markup\sitemap\java\sitemap.xsl, > > > I found the map:label element for setting a view label, > > > in a pipeline at any point. > > > > > > Thus I changed the documentation pipelines to: > > > > > > > > > > > > > > > > > > > > > > > > > Maybe the sitemap schema changed, but as I designed it, the label was an > > attribute, not an element. > > > > So you'd do > > > > > > > > > > instead. (but don't guarantee you that it works since not many people > > know even the existance of views so not much bugfixing on that side, > > yet!) > > I found this little treasure a while ago. The docs state the attribute label > in the map:components section but map:label for somewhere inside the pipeline. > Unfortunately I found that this is not working for aggregated content and/or subsitemaps. > I think this is a very handy feature for development. It would be great > to make this work also with aggregated content and sub sitemaps. I've talked to Stefano (he is my guest for some days here) about the map:label stuff and we found that the approach was wrong. It should be an attribute. I'll take care of fixing it in the 2.1 branch and as soon as we found it working correctly as we think it should I'll backport it to the 2.0 branch. Any objections? Giacomo --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org