RE: Woody textareas?

-Original Message- From: Simon Price [mailto:[EMAIL PROTECTED] Sent: Montag, 30. Juni 2003 20:04 ... Cocoon's form handling is (imho) it's weakest area at present although it is rapidly improving with the interplay between flow and xmlform. ... Simon Luke Penca wrote: Are

RE: Cocoon 2.1 migration problem with sub-sitemap

Did you add map:pipes to the map:components section in the root sitemap? -Original Message- From: Peter Klotz [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 18. Juni 2003 11:48 To: [EMAIL PROTECTED] Subject: Cocoon 2.1 migration problem with sub-sitemap Hi, I have migrated a

RE: retaining data from a partial pipeline for subsequent requests

-Original Message- From: Anoop Aryal [mailto:[EMAIL PROTECTED] ... Wishful/hopeful thinking: - something like this would be optimal: Generators:A B C | | |

RE: extracting xml-code out of a relational database

-Original Message- From: [EMAIL PROTECTED] I'm using Cocoon 2.1m2. I tried to use a logicsheet with esql and its esql:get-xml but I'm getting only undefined errors when trying to access the data of the text field. esql:get-xml is broken in M2. You need to get esql.xsl from

RE: Basic authentication

This sort of thing is usually done by an upstream Apache or in the servlet engine (Tomcat) configuration. If you really want to do it in Cocoon, you can write an action checking the BA header and use it in the sitemap to either deliver the resource or the auth-required (403) response. HTH,

Eclipse compiler and complex XSPs

I am currently trying M2 to prepare our Cocoon based websites for 2.1final and came across a problem with the Eclipse compiler. Out most complex XSP+logicsheet fails with the message: = org.apache.cocoon.ProcessingException: Language

RE: conditional cincludes?

Or cinclude another pipeline match to return a XML dummy file cinclude src=cocoon:/maybeexists/foo.xml/ map:match pattern=maybeexists/** map:act type=resource-exists src={1} map:generate type=file src={../1}/ map:serialize type=xml/ /map:act map:generate type=file

RE: pass parameters to internal pipeline

Try this: map:match pattern=test/ParamToAgg.xml map:generate src=cocoon:/test/getParam.xml/paramTest=a param value 9876/ map:serialize type=xml/ /map:match map:match pattern=test/getParam.xml/*=* map:generate src=myDev/test/dummy.xml/ map:transform src=myDev/xsl/getParam.xsl

RE: redirect's never return...

I think that you assume that cocoon:/directory/../_navigation.xml should be contracted to cocoon:/_navigation.xml and therefore match the first pattern. (Cocoon doesn't do this contraction for the good reason that /foo/bar/.. is not the same as /foo if /foo/bar is a symbolic link.) So what is

RE: Pass custom parameters into an XSP

Actually, you don't need to override setup(). The base class ofthe XSP generated class already does that and provides "protected Parameters parameters;" You can use directly in xsp:logic String entityType = this.parameters.getParameter("entityType"); including the other nice features of

RE: Simple XSP Ordering Problem

-Original Message- From: Sonny Sukumar [mailto:[EMAIL PROTECTED]] Sent: Montag, 14. Oktober 2002 21:56 To: [EMAIL PROTECTED] Subject: Simple XSP Ordering Problem Product xsp:logic String productId = xsp-request:get-parameter name=productid default=/; /xsp:logic ... Try: