You can use ParameterNameAware. The params interceptor has ways to
block/allow parameters based on regular expressions also.

musachy

On Thu, Dec 11, 2008 at 1:33 PM, stanlick <stanl...@gmail.com> wrote:
>
> I am aware that OGNL will convert incoming parameters and apply them to the
> business model in my action.  However, I would like to leverage role based
> permissions so that only authorized parameters are processed.  What is the
> prescribed solution for this?
>
> Scott
> --
> View this message in context: 
> http://www.nabble.com/How-to-secure-which-HTTP-parameters-should-be-graphed-onto-model-tp20961604p20961604.html
> Sent from the Struts - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
>



-- 
"Hey you! Would you help me to carry the stone?" Pink Floyd

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org

Reply via email to