This is kind of weird in that it's going to blow away any existing preference that wasn't set as a parameter on the `ActionRequest`.  Seems like a trip hazard for the poor guy who eventually tries to add a regular old portlet preference to this portlet.  Worth namespacing portlet preferences that behave in this way?  Worth only setting preference values for parameters actually present on the request?