Hi,
Why not create a service to allow named parameters? I see no
reason that named parameters, presented in a Map cannot be squeezed
and unsqueezed.
It needs 3 classes, a Service and an ILink implementation and a
custom PageLink component
The main stumbling block is that ILink construction in a service is
made via a method that accepts an array of service parameters and not
a map.
Simply add API, accessible to the PageLink component that accepts a
Map to construct an ILink.
When decoding the parameters in the service implementation you can
stuff them into the request cycle as attributes or, if the parameters
have
the same name as page properties use OGNL to set the properties from
the parameters.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
