Re: [S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh?

On 4/21/2018 3:05 PM, Martin Gainty wrote: > i could'nt find it in servlet-api spec? > > https://tomcat.apache.org/tomcat-8.0-doc/servletapi/javax/servlet/http/HttpServletResponse.html > > HttpServletResponse (Servlet 3.1 API Documentation >

Re: [S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh?

day, April 18, 2018 2:57 AM To: user@struts.apache.org Subject: Re: [S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh? On 4/18/2018 1:21 AM, Martin Gainty wrote: > MG>AFAIK a redirect terminates the old session and creates a new session I think redirect to same

Re: [S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh?

On 4/18/2018 5:27 PM, Martin Gainty wrote: > MG2>some confusion on where session is accessed > * available. This is because actions are built on a single-thread model. The > * only way to pass data is through the session > MG2>with chain interceptor No it didn't mean "with chain interceptor"

Re: [S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh?

ait Interceptor // Only re-submit token parameters on refresh? On 4/18/2018 1:21 AM, Martin Gainty wrote: > MG>AFAIK a redirect terminates the old session and creates a new session I think redirect to same domain:ip in same browser tab page should keep session. MG2>2 alternatives: build out

Re: [S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh?

On 4/18/2018 1:21 AM, Martin Gainty wrote: > MG>AFAIK a redirect terminates the old session and creates a new session I think redirect to same domain:ip in same browser tab page should keep session. > MG>a better alternative is to implement ChainingInterceptor with type="chain"> e.g. As

Re: [S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh?

From: Burton Rhodes <burtonrho...@gmail.com> Sent: Tuesday, April 17, 2018 7:23 AM To: Struts Users Mailing List Subject: Re: [S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh? That's a great thought. I think the session

Re: [S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh?

On 4/17/2018 3:53 PM, Burton Rhodes wrote: > That's a great thought. I think the session method makes more sense. Glad to hear :) thanks! I would like to add that you also can delete ExecAndWait interceptor. Then just save posted data in db and immediately send a thank you message to your

Re: [S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh?

That's a great thought. I think the session method makes more sense. On Tue, Apr 17, 2018 at 2:12 AM, Yasser Zamani wrote: > > > On 4/17/2018 6:42 AM, Burton Rhodes wrote: > > Also, How would I include everything except the email body field with the > > s:url tag? > >

Re: [S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh?

On 4/17/2018 6:42 AM, Burton Rhodes wrote: > Also, How would I include everything except the email body field with the > s:url tag? Unfortunately, I couldn't find a simple way :( However, as a workaround, instead, in your email form jsp, could you put the email body field as a POST param and

Re: [S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh?

Yes. I believe this is the case. Let me see if I can track down an example that breaks. Right now I just have reports of this happening but I haven’t been able to reproduce on my end yet. Also, How would I include everything except the email body field with the s:url tag? Thanks, Burton On

Re: [S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh?

On 4/15/2018 11:39 PM, Burton Rhodes wrote: > I have been getting "Bad Request" or "URL too long" errors on occasion for > an email form that uses the execute and wait interceptor. I am using the > to resubmit the form per the documentation. > > "/> > > However, the original form submits via

[S2] ExecuteAndWait Interceptor // Only re-submit token parameters on refresh?

I have been getting "Bad Request" or "URL too long" errors on occasion for an email form that uses the execute and wait interceptor. I am using the to resubmit the form per the documentation. "/> However, the original form submits via POST and the meta tag uses GET which I believe is the