Re: Struts2 validation problem

2010-04-04 Thread zud
newton.dave wrote: > > zud wrote: >> 1) Is old errors is not getting cleared that means when the filed value >> is >> empty when i submit the form it shows required that is ok and agian when >> i >> submit with empty values again now it shows messages like >> filed is required >> filed is requi

Re: Struts2 validation problem

2010-04-04 Thread zud
zud wrote: > > > > newton.dave wrote: >> >> zud wrote: >>> 1) Is old errors is not getting cleared that means when the filed value >>> is >>> empty when i submit the form it shows required that is ok and agian >>> when i >>> submit with empty values again now it shows messages like >>> file

Re: Struts2 validation problem

2010-04-04 Thread zud
zud wrote: > > > > newton.dave wrote: >> >> zud wrote: >>> 1) Is old errors is not getting cleared that means when the filed value >>> is >>> empty when i submit the form it shows required that is ok and agian >>> when i >>> submit with empty values again now it shows messages like >>> file

Re: Struts2 validation problem

2010-04-04 Thread zud
newton.dave wrote: > > zud wrote: >> 1) Is old errors is not getting cleared that means when the filed value >> is >> empty when i submit the form it shows required that is ok and agian when >> i >> submit with empty values again now it shows messages like >> filed is required >> filed is requ

Re: Struts2 validation problem

2010-04-03 Thread Dave Newton
zud wrote: 1) Is old errors is not getting cleared that means when the filed value is empty when i submit the form it shows required that is ok and agian when i submit with empty values again now it shows messages like filed is required filed is required Are you using Spring as your object fac

Re: Struts2 Validation Problem - validation errors not being cleared when corrected!

2009-10-23 Thread Murray Furtado
Hehe, I've just resolved my own issue! The problem was my spring configuration. I needed to specify scope="prototype" on each of my Struts 2 Action declarations. Singleton actions were being created and thus previous field errors were being carried over between requests. I'm surprised this isn't a