I would use an input module rather then a map:select.
why don't you have
and depending on parameters, your {my-parameter-checker} input-module retuns a
different value.
Ard
> >
> >In fact, this didn't work:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >It seems to always do the oth
Thanks to both Grzegorz Kossakowski and Andrew Stevens
who both pointed me to RequestParameterExistsAction.
This does exactly what I want:
uri="cocoon://vivaead/entity-resolver?document=published/{../1}/{../
2}.xml&entity=unparsed-entity-uri" />
From: "Steven D. Majewski" <[EMAIL PROTECTED]>
Date: Sat, 3 Mar 2007 10:59:51 -0500
In fact, this didn't work:
It seems to always do the otherwise.
Is there another way to select on the presence
( rather than the value ) of a request param ?
How about
org.apache.cocoon.acting.Re
In fact, this didn't work:
It seems to always do the otherwise.
Is there another way to select on the presence
( rather than the value ) of a request param ?
-- Steve Majewski
On Mar 3, 2007, at 10:37 AM, Steven D. Majewski wrote:
In the docs and examples for the request-par
Steven D. Majewski napisał(a):
[...]
Is there any way to select in the sitemap based on the
presence of ANY request parameters ?
The current situation is little bit confusing and limited because null
values and empty strings usually are treated as equal in sitemap's
expressions/conditions.
In the docs and examples for the request-parameter selector,
the selection tests are done on the value of a particular request-
parameter
...
...
...
But what I want to do is select different processing
depending on the presence of a request parameter:
if
