On Wednesday 02 June 2010 18:14:29 Dale Newfield wrote:
> On 6/2/10 7:29 AM, RogerV wrote:
> > I'm using the Exec&Wait interceptor in a couple of places. I've noticed
> > that while the long running process is in progress, every time the wait
> > screen polls the action I get [WARN,TokenHelper] Could not find token
> > mapped to token name struts.token in my logs.
>
> ExecuteAndWaitInterceptor.java contains:
> if (TokenHelper.getToken() != null) {
> session.put(TokenHelper.getTokenName(),
> TokenHelper.getToken());
> }
>
> And getToken() calls getToken("struts.token"), which leads to:
> TokenHelper.java line 108: LOG.warn("Could not find token mapped to
> token name " + tokenName);
>
> If you're not using the token stuff at all and just want to eliminate
> the log messages, you could change the log levels on
> org.apache.struts2.util.TokenHelper...
>
I was more, kind of wondering, what does using exec&wait with Token support
buy me over using exec&wait without Token support? (I've never used the in-
built token support before)
As an aside, how are people polling the action for completion. I'm using the
meta-refresh tag and this gives me an annoying "blink" effect - has anyone
managed to turn this into an "ajax-y" poll?
Regards
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
