i tried solution 4 where the action:
- has the DTO itself as an instance variable (as opposed to having DTO
fields as instance variables)
- implements ParameterNameAware
it works ok with regard to parameter interception but the parameters are not
checked by validation annotations. this is because
The documentation for the ParametersInterceptor [1] mentions the
ParameterNameAware interface [2]. Maybe that could be a solution?
Nils-H
[1] - http://struts.apache.org/2.1.6/docs/parameters-interceptor.html
[2] -
http://struts.apache.org/2.1.6/struts2-core/apidocs/com/opensymphony/xwork2/interc
I would go for #4, you might want to look into
http://struts.apache.org/2.0.6/struts2-core/apidocs/com/opensymphony/xwork2/interceptor/ParameterNameAware.html,
or blocking params in the params interceptor.
musachy
On Mon, Mar 23, 2009 at 8:53 AM, José Santos wrote:
> hi,
>
> what's the recommend
hi,
what's the recommended design for avoiding fields of DTOs in the value stack
being updated through (HTML) DOM manipulation?
consider a typical edit page containing a form with some fields. this page
is a visual representation of a DTO we are about to update. the DTO is set
in the action - it
4 matches
Mail list logo
