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 2010/11/16 21:58:15 UTC

[jira] Resolved: (WICKET-3175) Radio uuid is calculated wrongly for heavy instalations.

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

Igor Vaynberg resolved WICKET-3175.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5-M4
                   1.4.14

> Radio uuid is calculated wrongly for heavy instalations.
> --------------------------------------------------------
>
>                 Key: WICKET-3175
>                 URL: https://issues.apache.org/jira/browse/WICKET-3175
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.13
>            Reporter: Michał Letyński
>            Assignee: Igor Vaynberg
>             Fix For: 1.4.14, 1.5-M4
>
>         Attachments: radioproblem.tgz, WICKET-3175.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> On big page's autoIndex for Page is getting bigger. Autoindex is used for radio buttons to identify its value (return "radio" + uuid).
> Uuid is a short primitive type and when its bigger then 32767 it become negative. Its a problem for radio button getValue code which looks like this:
> 	public String getValue()
> 	{
> 		if (uuid < 0)
> 		{
> 			uuid = getPage().getAutoIndex();
> 		}
> 		return "radio" + uuid;
> 	}
> In such case new uuid is set and we will get an error after submit this radio:
> "WicketMessage: submitted http post value [radio-32768] for RadioGroup component [0:form:radioGroup] is illegal because it does not contain relative path to a Radio componnet. Due to this the RadioGroup component cannot resolve the selected Radio component pointed to by the illegal value. A possible reason is that componment hierarchy changed between rendering and form submission."
> Problem can be solved by changing short primitive type to Short object and checking its not null instead of <0.

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