You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2009/09/23 00:47:16 UTC

[jira] Resolved: (WICKET-2478) TabbedPanel rendering bug

     [ https://issues.apache.org/jira/browse/WICKET-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-2478.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5-M1
                   1.4.2
         Assignee: Igor Vaynberg

> TabbedPanel rendering bug
> -------------------------
>
>                 Key: WICKET-2478
>                 URL: https://issues.apache.org/jira/browse/WICKET-2478
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 1.4.1
>            Reporter: Pedro Santos
>            Assignee: Igor Vaynberg
>             Fix For: 1.4.2, 1.5-M1
>
>         Attachments: patch.txt, tabbedpaneltestel.jar
>
>
> In my application I have on TabbedPanel component that has no tab ( will to be removed since make no sense ). Any way, at some point I put the component to an AjaxRequestTarget response, an when the tabbed panel was re-rendered, it throw an java.lang.ArrayIndexOutOfBoundsException: 0 (I'm sending an test case attached)
> The problem is that on isTabVisible method, an visibility variable receive the visibility on cache using the tabIndex:
> Boolean visible = tabsVisibilityCache[tabIndex];
> at this moment, the tabsVisibility is empty ( and tabIndex == 0 )
> in my workspace I resolve the exception testing the array lenght (I'm sending a path)
> although is an rare occurrence bug, I think wicket should provide an  solution.

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