You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "jWeekend (JIRA)" <ji...@apache.org> on 2009/01/21 22:39:59 UTC
[jira] Created: (WICKET-2037) Should adding AJAX behaviur to a page
make i stateful?
Should adding AJAX behaviur to a page make i stateful?
-------------------------------------------------------
Key: WICKET-2037
URL: https://issues.apache.org/jira/browse/WICKET-2037
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.3.5
Environment: Any
Reporter: jWeekend
Priority: Minor
Attachments: quickstart.zip
For full history see see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
Igor,
I've had a look at Wayne's quickstart.
The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
If you change the BookmarkablePageLink to a PageLink things work as expected.
It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
The result is the same with both 1.3.5 and 1.4-rc1.
See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
Regards - Cemal
jWeekend
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2037) Should adding AJAX behaviur to a page
make i stateful?
Posted by "jWeekend (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jWeekend updated WICKET-2037:
-----------------------------
Description:
For full history see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
Igor,
I've had a look at Wayne's quickstart.
The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
If you change the BookmarkablePageLink to a PageLink things work as expected.
It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
The result is the same with both 1.3.5 and 1.4-rc1.
See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
Regards - Cemal
http://www.jWeekend.co.uk
was:
For full history see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
Igor,
I've had a look at Wayne's quickstart.
The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
If you change the BookmarkablePageLink to a PageLink things work as expected.
It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
The result is the same with both 1.3.5 and 1.4-rc1.
See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
Regards - Cemal
<a href="http://www.jWeekend.co.uk>jWeekend</a>
> Should adding AJAX behaviur to a page make i stateful?
> -------------------------------------------------------
>
> Key: WICKET-2037
> URL: https://issues.apache.org/jira/browse/WICKET-2037
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.5
> Environment: Any
> Reporter: jWeekend
> Priority: Minor
> Attachments: quickstart.zip
>
>
> For full history see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
> Igor,
> I've had a look at Wayne's quickstart.
> The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
> If you change the BookmarkablePageLink to a PageLink things work as expected.
> It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
> The result is the same with both 1.3.5 and 1.4-rc1.
> See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
> Regards - Cemal
> http://www.jWeekend.co.uk
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2037) Should adding AJAX behaviur to a page
make i stateful?
Posted by "jWeekend (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jWeekend updated WICKET-2037:
-----------------------------
Description:
For full history see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
Igor,
I've had a look at Wayne's quickstart.
The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
If you change the BookmarkablePageLink to a PageLink things work as expected.
It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
The result is the same with both 1.3.5 and 1.4-rc1.
See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
Regards - Cemal
jWeekend
was:
For full history see see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
Igor,
I've had a look at Wayne's quickstart.
The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
If you change the BookmarkablePageLink to a PageLink things work as expected.
It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
The result is the same with both 1.3.5 and 1.4-rc1.
See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
Regards - Cemal
jWeekend
> Should adding AJAX behaviur to a page make i stateful?
> -------------------------------------------------------
>
> Key: WICKET-2037
> URL: https://issues.apache.org/jira/browse/WICKET-2037
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.5
> Environment: Any
> Reporter: jWeekend
> Priority: Minor
> Attachments: quickstart.zip
>
>
> For full history see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
> Igor,
> I've had a look at Wayne's quickstart.
> The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
> If you change the BookmarkablePageLink to a PageLink things work as expected.
> It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
> The result is the same with both 1.3.5 and 1.4-rc1.
> See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
> Regards - Cemal
> jWeekend
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2037) Should adding AJAX behaviur to a page
make i stateful?
Posted by "jWeekend (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jWeekend updated WICKET-2037:
-----------------------------
Description:
For full history see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
Igor,
I've had a look at Wayne's quickstart.
The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
If you change the BookmarkablePageLink to a PageLink things work as expected.
It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
The result is the same with both 1.3.5 and 1.4-rc1.
See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
Regards - Cemal
<a href="http://www.jWeekend.co.uk>jWeekend</a>
was:
For full history see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
Igor,
I've had a look at Wayne's quickstart.
The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
If you change the BookmarkablePageLink to a PageLink things work as expected.
It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
The result is the same with both 1.3.5 and 1.4-rc1.
See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
Regards - Cemal
jWeekend
> Should adding AJAX behaviur to a page make i stateful?
> -------------------------------------------------------
>
> Key: WICKET-2037
> URL: https://issues.apache.org/jira/browse/WICKET-2037
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.5
> Environment: Any
> Reporter: jWeekend
> Priority: Minor
> Attachments: quickstart.zip
>
>
> For full history see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
> Igor,
> I've had a look at Wayne's quickstart.
> The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
> If you change the BookmarkablePageLink to a PageLink things work as expected.
> It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
> The result is the same with both 1.3.5 and 1.4-rc1.
> See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
> Regards - Cemal
> <a href="http://www.jWeekend.co.uk>jWeekend</a>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2037) Should adding AJAX behaviur to a page
make it stateful?
Posted by "jWeekend (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jWeekend updated WICKET-2037:
-----------------------------
Summary: Should adding AJAX behaviur to a page make it stateful? (was: Should adding AJAX behaviur to a page make i stateful? )
> Should adding AJAX behaviur to a page make it stateful?
> --------------------------------------------------------
>
> Key: WICKET-2037
> URL: https://issues.apache.org/jira/browse/WICKET-2037
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.5
> Environment: Any
> Reporter: jWeekend
> Priority: Minor
> Attachments: quickstart.zip
>
>
> For full history see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
> Igor,
> I've had a look at Wayne's quickstart.
> The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
> If you change the BookmarkablePageLink to a PageLink things work as expected.
> It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
> The result is the same with both 1.3.5 and 1.4-rc1.
> See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
> Regards - Cemal
> http://www.jWeekend.co.uk
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-2037) Should adding AJAX behaviour to a
page make it stateful?
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-2037.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4-RC2
1.3.6
Assignee: Igor Vaynberg
> Should adding AJAX behaviour to a page make it stateful?
> ---------------------------------------------------------
>
> Key: WICKET-2037
> URL: https://issues.apache.org/jira/browse/WICKET-2037
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.5
> Environment: Any
> Reporter: jWeekend
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.3.6, 1.4-RC2
>
> Attachments: quickstart.zip
>
>
> For full history see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
> Igor,
> I've had a look at Wayne's quickstart.
> The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
> If you change the BookmarkablePageLink to a PageLink things work as expected.
> It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
> The result is the same with both 1.3.5 and 1.4-rc1.
> See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
> Regards - Cemal
> http://www.jWeekend.co.uk
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2037) Should adding AJAX behaviour to a
page make it stateful?
Posted by "jWeekend (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jWeekend updated WICKET-2037:
-----------------------------
Summary: Should adding AJAX behaviour to a page make it stateful? (was: Should adding AJAX behaviur to a page make it stateful? )
> Should adding AJAX behaviour to a page make it stateful?
> ---------------------------------------------------------
>
> Key: WICKET-2037
> URL: https://issues.apache.org/jira/browse/WICKET-2037
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.5
> Environment: Any
> Reporter: jWeekend
> Priority: Minor
> Attachments: quickstart.zip
>
>
> For full history see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
> Igor,
> I've had a look at Wayne's quickstart.
> The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
> If you change the BookmarkablePageLink to a PageLink things work as expected.
> It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
> The result is the same with both 1.3.5 and 1.4-rc1.
> See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
> Regards - Cemal
> http://www.jWeekend.co.uk
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2037) Should adding AJAX behaviur to a page
make i stateful?
Posted by "jWeekend (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jWeekend updated WICKET-2037:
-----------------------------
Attachment: quickstart.zip
> Should adding AJAX behaviur to a page make i stateful?
> -------------------------------------------------------
>
> Key: WICKET-2037
> URL: https://issues.apache.org/jira/browse/WICKET-2037
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.5
> Environment: Any
> Reporter: jWeekend
> Priority: Minor
> Attachments: quickstart.zip
>
>
> For full history see see http://www.nabble.com/Using-AbstractDefaultAjaxBehavior-on-a-Bookmarkable-page--td21562119.html
> Igor,
> I've had a look at Wayne's quickstart.
> The problem he hit is that if a page, P, with a no-args constructor (ie P is "bookmarkable") has an AJAX behaviour added to it and P is arrived at via a BookmarkablePageLink on some other page, then Wicket can't find that P instance in the session to handle any callbacks and delivers the infamous "Page Expired" page. If you add the same AJAX behaviour to a label on P, then the callback works.
> If you change the BookmarkablePageLink to a PageLink things work as expected.
> It's almost as if, when the the page is created due to a click on a BookmarkableLink, Wicket is deciding it only needs to consider the page stateful if it contains components that have callbacks/ajax-bahaviours, but if there are none, it doesn't bother checking the page object itself for such callbacks. Is that what you'd expect?
> The result is the same with both 1.3.5 and 1.4-rc1.
> See the attached quickstart which is the simplest example I could make to demonstrate what Wayne sent me.
> Regards - Cemal
> jWeekend
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.