struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maurizio Cucchiara <maurizio.cucchi...@gmail.com>
Subject Re: Have you ever used InputConfig annotation?
Date Sat, 06 Nov 2010 07:36:20 GMT
InputConfig works as documented. I reccomend to use Li's suggestion
for inheritance matter. When you need to overwrite base class
behavior, then mark method with InputConfig annotation.

2010/11/5 Alfredo Manuel Osorio Martinez <alfredo.osorio@afirme.com>:
> Hello,
>
> By looking at DefaultWorkflowInterceptor I saw an annotation that I
> didn't know existed. I am talking about:
>
> com.opensymphony.xwork2.interceptor.annotations.InputConfig
>
> I think it can be used for input repopulation and can be used as an
> alternative to Preparable and <s:action/>.
>
> What surprised me was that there is a little documentation about the use
> of the annotation or examples.
>
> Haver you ever used this one before?
>
> Is it a good idea to use it for input repopulation for example
> collections for selects in case a validation fails?
>
> Thanks
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>



-- 
Maurizio Cucchiara

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


Mime
View raw message