>> That could work, but the problem is that the parameters names are mapped
to
>> various meta-data and I don't know which ones I want and which ones I
don't
>> want until I examine the meta-data. Moving the management of the
metadata
>> into an XSLT would in effect mean moving converting a chunk
Hunsberger, Peter wrote:
> That could work, but the problem is that the parameters names are mapped to
> various meta-data and I don't know which ones I want and which ones I don't
> want until I examine the meta-data. Moving the management of the metadata
> into an XSLT would in effect mean movi
> Is there some reason which forces you not to copy the
> parameters wholesale? Otherwise, use use-request-parameters
> and simply ignore the parameters you don't want.
Should have made that clear; if I pass all parameters I can clobber
parameters where I don't want the values from the form. Al
Hunsberger, Peter wrote:
> I've got a situation where I've got to pass a bunch of parameters with
> unknown names from a (Cocoon generated) HTML form through an action to a
> standard Cocoon pipeline. There are certain parameters I don't want to pass
> on to the stylesheet so I can't use
>
>
I've got a situation where I've got to pass a bunch of parameters with
unknown names from a (Cocoon generated) HTML form through an action to a
standard Cocoon pipeline. There are certain parameters I don't want to pass
on to the stylesheet so I can't use
However, I can, in my
