Thanks Dale, that was a very informative mail. I used chain result type just
for a better separation of actions and till
now it did not seem to have any undesirable effect. Anyway I 'll try a new
approach to the problem and I 'll avoid using
chain result type. Thanks all for the help.
On Wed, May
I believe that your problem isn't with execAndWait -- it's with the
chain result type. The way that execAndWait works is that there's only
one job runnable at a time in any given session with any given action
name. The intermediate requests don't need the arguments as it's just
using the acti
Am 05.05.2010 12:42, schrieb Yiorgos Panayiotakis:
Thank you,
Though I have little experience in web development I was aware of that, but
I avoided using
sessions due to the fact that a user could open multiple tabs in a browser
and issue multiple
requests that would belong to the same session. S
Thank you,
Though I have little experience in web development I was aware of that, but
I avoided using
sessions due to the fact that a user could open multiple tabs in a browser
and issue multiple
requests that would belong to the same session. So if he tried to refresh an
older request this
would
Hi,
you can store data in session and retrieve it later on. Data stored in
session is persisted through requests.
ActionContext.getContext().getSession();
http://struts.apache.org/2.1.8.1/struts2-core/apidocs/com/opensymphony/xwork2/ActionContext.html
Hi,
I have an issue in my code that I
Hi,
I have an issue in my code that I can't resolve and I would appreciate your
help.
I am using the struts2 execAndWait interceptor when I submit a form on my
site.
Below is the relevant struts.xml snippet
/jsp/unscheduled.jsp
6 matches
Mail list logo
