Hi,
I assume, since it doesn't call any action class if validation fails,
stack got only values from jsp which are already populated into bean
properties when we submit before valdiation.
Since bean is not in session, it should not have any values.
But we have already submitted the form so thats
Flow in my project works like this.
When user request one web page, action method searchPm will execute.
This calls populatePm method in service call.
Then it will call some dao methods.
I have JavaBean as a property in action class. This java bean get populated
in service(dao) and return from the
I'm guessing that you have something like
this.myList = populateList();
inside your execute() method. When validation fails, it just sends you back
to the jsp without redoing execute(), so of course the list will be null.
-Brian
On Tue, Jan 26, 2010 at 10:26 AM, nani2ratna wrote:
>
> Hi Br
Hi Brian,
I have seen that interface.
If I got more than one action method in one action class.
Then when ever you execute/call method(action) in that action class,
this prepare method will be called and this setting of list will be
executed.
But My main question why the list setting to null valu
You might look into using the Preparable interface [1]. It's useful for
these types of situations; just add the code to generate the list into a
prepare() method on your action class instead of in execute().
Hope this helps,
-Brian
[1] -
http://www.opensymphony.com/xwork/api/com/opensymphony/xw
5 matches
Mail list logo
