You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Major Peter (JIRA)" <ji...@apache.org> on 2010/08/15 17:14:16 UTC

[jira] Created: (WICKET-2990) AjaxFallbackLink with NonCachingImage makes component state-unaware

AjaxFallbackLink with NonCachingImage makes component state-unaware
-------------------------------------------------------------------

                 Key: WICKET-2990
                 URL: https://issues.apache.org/jira/browse/WICKET-2990
             Project: Wicket
          Issue Type: Bug
          Components: wicket
    Affects Versions: 1.5-M1
            Reporter: Major Peter


If you have an AjaxFallbackLink containing a NonCachingImage, then if your onClick stores some state in the link object, then this change will be lost on the next click.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (WICKET-2990) AjaxFallbackLink with NonCachingImage makes component state-unaware

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

Igor Vaynberg resolved WICKET-2990.
-----------------------------------

      Assignee: Igor Vaynberg
    Resolution: Cannot Reproduce

can no longer reproduce with 1.5-snapshot

> AjaxFallbackLink with NonCachingImage makes component state-unaware
> -------------------------------------------------------------------
>
>                 Key: WICKET-2990
>                 URL: https://issues.apache.org/jira/browse/WICKET-2990
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5-M1
>            Reporter: Major Peter
>            Assignee: Igor Vaynberg
>         Attachments: wicket-2990.tar.gz
>
>
> If you have an AjaxFallbackLink containing a NonCachingImage, then if your onClick stores some state in the link object, then this change will be lost on the next click.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-2990) AjaxFallbackLink with NonCachingImage makes component state-unaware

Posted by "Major Peter (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901487#action_12901487 ] 

Major Peter commented on WICKET-2990:
-------------------------------------

Probably this was caused by WICKET-2988, which is now fixed. Thanks!

> AjaxFallbackLink with NonCachingImage makes component state-unaware
> -------------------------------------------------------------------
>
>                 Key: WICKET-2990
>                 URL: https://issues.apache.org/jira/browse/WICKET-2990
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5-M1
>            Reporter: Major Peter
>            Assignee: Igor Vaynberg
>         Attachments: wicket-2990.tar.gz
>
>
> If you have an AjaxFallbackLink containing a NonCachingImage, then if your onClick stores some state in the link object, then this change will be lost on the next click.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-2990) AjaxFallbackLink with NonCachingImage makes component state-unaware

Posted by "Major Peter (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898697#action_12898697 ] 

Major Peter commented on WICKET-2990:
-------------------------------------

Note if the setDefaultModel calls are removed from onClick, then the stdout shows correct values.

> AjaxFallbackLink with NonCachingImage makes component state-unaware
> -------------------------------------------------------------------
>
>                 Key: WICKET-2990
>                 URL: https://issues.apache.org/jira/browse/WICKET-2990
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5-M1
>            Reporter: Major Peter
>         Attachments: wicket-2990.tar.gz
>
>
> If you have an AjaxFallbackLink containing a NonCachingImage, then if your onClick stores some state in the link object, then this change will be lost on the next click.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WICKET-2990) AjaxFallbackLink with NonCachingImage makes component state-unaware

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

Major Peter updated WICKET-2990:
--------------------------------

    Attachment: wicket-2990.tar.gz

Simple quickstart reproducing the problem.
Usage:
mvn jetty:run
click on the image more then once, the pic should be work as a toggle so on/off states after each other.
I've tried to create a TestCase for this, but again the test worked, and the browser didn't.
This project could be easily backported to 1.4.10, with which it's working.

> AjaxFallbackLink with NonCachingImage makes component state-unaware
> -------------------------------------------------------------------
>
>                 Key: WICKET-2990
>                 URL: https://issues.apache.org/jira/browse/WICKET-2990
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5-M1
>            Reporter: Major Peter
>         Attachments: wicket-2990.tar.gz
>
>
> If you have an AjaxFallbackLink containing a NonCachingImage, then if your onClick stores some state in the link object, then this change will be lost on the next click.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.