Aggregate:
1. a request document from the RequestGenerator
2. a representation of the schema of the dynamically-generated form
see
http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/generation/RequestGenerator.html
The same applies to populating the dynamically-generated form with
default or existing values, so it may be worthwhile to first convert the
request document into a common format and then use a common merge transform.
Jeroen Reijn wrote:
Perhaps you use an aggregate and include a part that uses the request
generator?
Just my 2 cents...
Jeroen
ypomonh wrote:
Thanks Jasha but unfortunately that works fine as long as you know
what parameters to expect. If you don't (eg. a dynamically generated
form) you can't reference them by name.
In flowscript you have getParameterNames() from where you can iterate
them. I need something similar in the sitemap...
Jasha Joachimsthal wrote:
Within your map:generate or map:transform:
<map:parameter name="paramName" value="{request-param:paramName}"/>
Is it possible for a certain pipeline to accept multiple request
parameters and handle them (like in a map) without calling
flowscript and getParameterNames()..?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
