--- Olivier Billard <[EMAIL PROTECTED]> wrote:
Hi Oscar,
You can use a request attribute.
-- Olivier Billard
Oscar Picasso wrote:
Hi,
Is there a way to get, inside an XSP page, the returned map from an action
?
I know that we can pass the individual map elements as parameters, but I
would
like to have a more generic XSP page that would process the entire map, no matter what are its actual elements.
Thanks.
Oscar
I should have added that I don't want to use request or session attributes.
If I use them I have to ensure that other portions of the pipeline doesn't use the same name attribute for their own purpose.
The nice thing about <map:parameter ...> is that the scope of your parameter is limited to the portion of the pipeline where it is used.
But the bad thing is that these are only string...
If you properly name your attribute (prefix it by something specific by the pipeline), you won't have a collision.
For me, using request attributes is the cleanest way to go.
It's up to you...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
