You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Flavio Souza (JIRA)" <ji...@apache.org> on 2012/07/27 01:43:33 UTC

[jira] [Created] (WICKET-4680) InvalidBehaviorIdException raised after session time out

Flavio Souza created WICKET-4680:
------------------------------------

             Summary: InvalidBehaviorIdException raised after session time out
                 Key: WICKET-4680
                 URL: https://issues.apache.org/jira/browse/WICKET-4680
             Project: Wicket
          Issue Type: Bug
          Components: wicket
    Affects Versions: 1.5.7
            Reporter: Flavio Souza


The issue happened after I tried the wicket-fullcalendar (https://github.com/42Lines/wicket-fullcalendar) component for wicket.

As I stated in an issue created in the github (https://github.com/42Lines/wicket-fullcalendar/issues/12), Wicket throws an "InvalidBehaviorIdException" in HomePage if I try to do any other ajax call after session time out.


Reproducing steps:
Run the examples project from wicket-fullcalendar, wait till' the session time out and do any other Fullcalendar AJAX call.


- This led me to some questions:
 + Wicket tries to recreate the behaviors after session time out?

 + According to Igor's comment:
        "without this setting wicket tries to be clever and when it sees the page is expired it tries to recreate it from the bookmarkable parameters, but this does not always bring the page into the correct state for a listener url to be invoked. if wicket sees a listener url it should not try to recreate the page even when the setting is enabled."
        + What do you mean by "if wicket sees a listener url it should not try to recreate the page even when the setting is enabled"? Wicket will handle the listener being invoked after session time out or no?

Thanks ;)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (WICKET-4680) InvalidBehaviorIdException raised after session time out

Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-4680.
-------------------------------------

    Resolution: Not A Problem

The problem is that FullCalendar component claims to be stateless while it actually is not, it uses special callbacks for its Ajax needs.

Adding 
@Override
	protected boolean getStatelessHint()
	{
		return false;
	}

to FullCalendar.java fixes the problem. With this Wicket just re-creates the HomePage after expiry as documented.
                
> InvalidBehaviorIdException raised after session time out
> --------------------------------------------------------
>
>                 Key: WICKET-4680
>                 URL: https://issues.apache.org/jira/browse/WICKET-4680
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.7
>            Reporter: Flavio Souza
>
> The issue happened after I tried the wicket-fullcalendar (https://github.com/42Lines/wicket-fullcalendar) component for wicket.
> As I stated in an issue created in the github (https://github.com/42Lines/wicket-fullcalendar/issues/12), Wicket throws an "InvalidBehaviorIdException" in HomePage if I try to do any other ajax call after session time out.
> Reproducing steps:
> Run the examples project from wicket-fullcalendar, wait till' the session time out and do any other Fullcalendar AJAX call.
> - This led me to some questions:
>  + Wicket tries to recreate the behaviors after session time out?
>  + According to Igor's comment:
>         "without this setting wicket tries to be clever and when it sees the page is expired it tries to recreate it from the bookmarkable parameters, but this does not always bring the page into the correct state for a listener url to be invoked. if wicket sees a listener url it should not try to recreate the page even when the setting is enabled."
>         + What do you mean by "if wicket sees a listener url it should not try to recreate the page even when the setting is enabled"? Wicket will handle the listener being invoked after session time out or no?
> Thanks ;)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira