[jira] Updated: (WICKET-1621) Misleading example works despite error
[ https://issues.apache.org/jira/browse/WICKET-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank Silbermann updated WICKET-1621: - Attachment: screenshot-1.jpg Example should call "persons.setReuseItems(true);" as the ListView contains Form components. > Misleading example works despite error > -- > > Key: WICKET-1621 > URL: https://issues.apache.org/jira/browse/WICKET-1621 > Project: Wicket > Issue Type: Bug > Components: wicket-examples > Environment: not applicable >Reporter: Frank Silbermann >Priority: Minor > Attachments: screenshot-1.jpg > > > The resolution to Wicket-1601 is that anytime a ListView is used in a Form > and contains form components one should call #setReuseItems(true). The > JavaDoc for ListView indeed says this. > However, most people learn Wicket primarily by looking at the examples, and > the RadioGroup component example creates a ListView that contains form > components, but does not do this. (When I followed the example it worked > until I put two such RadioGroups on the same page.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (WICKET-1621) Misleading example works despite error
Misleading example works despite error -- Key: WICKET-1621 URL: https://issues.apache.org/jira/browse/WICKET-1621 Project: Wicket Issue Type: Bug Components: wicket-examples Environment: not applicable Reporter: Frank Silbermann Priority: Minor The resolution to Wicket-1601 is that anytime a ListView is used in a Form and contains form components one should call #setReuseItems(true). The JavaDoc for ListView indeed says this. However, most people learn Wicket primarily by looking at the examples, and the RadioGroup component example creates a ListView that contains form components, but does not do this. (When I followed the example it worked until I put two such RadioGroups on the same page.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1601) Two RadioGroups on one page interfering with one another
[ https://issues.apache.org/jira/browse/WICKET-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank Silbermann updated WICKET-1601: - Description: I created a simple Panel that contains a formatted RadioGroup with wantOnSelectionChangedNotifications() returning true. (Its constructor accepts an array of options, a PropertyModel to be controlled, and a caption for the label.) I put two instances of this panel on a single page, each controlling its own model variable. The page displays the two RadioGroup panels and displays the value of the two model variables. When I select a radiobutton from one group, all the radio buttons from the other group become unselected (i.e., the dot indicator disappears) -- as though the radio buttons belonged to the same button group. My quickstart project illustrating the behavior uses Wicket 1.3.3. Bring up the home page and begin clicking its radio groups to see the behavior. I discovered this problem in my Wicket 1.2 application when I tried to upgrade its libraries from Wicket 1.2.2 to Wicket 1.2.6. (With the new libraries, I also began seeing a great many puzzling new null value errors.) If the bug gets fixed in Wicket 1.3, I'll upgrade my application to it. was: I created a simple Panel that contains a formatted RadioGroup with wantOnSelectionChangedNotifications() returning true. (Its constructor accepts an array of options, a PropertyModel to be controlled, and a caption for the label.) I put two instances of this panel on a single page, each controlling its own model variable. The page displays the two RadioGroup panels and displays the value of the two model variables. When I select a radiobutton from one group, all the radio buttons from the other group become unselected (i.e., the dot indicator disappears) -- as though the radio buttons belonged to the same button group. My quickstart project illustrating the behavior (if I can figure out how to attach it) uses Wicket 1.3.3. Bring up the home page and begin clicking its radio groups to see the behavior. I discovered this problem in my Wicket 1.2 application when I tried to upgrade its libraries from Wicket 1.2.2 to Wicket 1.2.6. (With the new libraries, I also began seeing a great many puzzling new null value errors.) If the bug gets fixed in Wicket 1.3, I'll upgrade my application to it. > Two RadioGroups on one page interfering with one another > > > Key: WICKET-1601 > URL: https://issues.apache.org/jira/browse/WICKET-1601 > Project: Wicket > Issue Type: Bug >Affects Versions: 1.3.3 > Environment: generic >Reporter: Frank Silbermann > Attachments: myproject.zip, screenshot-1.jpg > > > I created a simple Panel that contains a formatted RadioGroup with > wantOnSelectionChangedNotifications() returning true. (Its constructor > accepts an array of options, a PropertyModel to be controlled, and a caption > for the label.) I put two instances of this panel on a single page, each > controlling its own model variable. The page displays the two RadioGroup > panels and displays the value of the two model variables. > When I select a radiobutton from one group, all the radio buttons from the > other group become unselected (i.e., the dot indicator disappears) -- as > though the radio buttons belonged to the same button group. > My quickstart project illustrating the behavior uses Wicket 1.3.3. Bring up > the home page and begin clicking its radio groups to see the behavior. > I discovered this problem in my Wicket 1.2 application when I tried to > upgrade its libraries from Wicket 1.2.2 to Wicket 1.2.6. (With the new > libraries, I also began seeing a great many puzzling new null value errors.) > If the bug gets fixed in Wicket 1.3, I'll upgrade my application to it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1601) Two RadioGroups on one page interfering with one another
[ https://issues.apache.org/jira/browse/WICKET-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank Silbermann updated WICKET-1601: - Attachment: screenshot-1.jpg Initially, both button groups had the first selection (Ay) chosen. Here, I clicked the third choice of the first group, changing the value of the first model variable. The second radio button group lost its indicator. > Two RadioGroups on one page interfering with one another > > > Key: WICKET-1601 > URL: https://issues.apache.org/jira/browse/WICKET-1601 > Project: Wicket > Issue Type: Bug >Affects Versions: 1.3.3 > Environment: generic >Reporter: Frank Silbermann > Attachments: myproject.zip, screenshot-1.jpg > > > I created a simple Panel that contains a formatted RadioGroup with > wantOnSelectionChangedNotifications() returning true. (Its constructor > accepts an array of options, a PropertyModel to be controlled, and a caption > for the label.) I put two instances of this panel on a single page, each > controlling its own model variable. The page displays the two RadioGroup > panels and displays the value of the two model variables. > When I select a radiobutton from one group, all the radio buttons from the > other group become unselected (i.e., the dot indicator disappears) -- as > though the radio buttons belonged to the same button group. > My quickstart project illustrating the behavior (if I can figure out how to > attach it) uses Wicket 1.3.3. Bring up the home page and begin clicking its > radio groups to see the behavior. > I discovered this problem in my Wicket 1.2 application when I tried to > upgrade its libraries from Wicket 1.2.2 to Wicket 1.2.6. (With the new > libraries, I also began seeing a great many puzzling new null value errors.) > If the bug gets fixed in Wicket 1.3, I'll upgrade my application to it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1601) Two RadioGroups on one page interfering with one another
[ https://issues.apache.org/jira/browse/WICKET-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank Silbermann updated WICKET-1601: - Attachment: myproject.zip I modified the QuickStart project to define a panel component constructed with an array of options for a radio button group, a String to label the group, and a PropertyModel so the RadioGroup can control the value of a variable. The component posts back on selection changes. The home page displays two instances of this panel, each radio button group controlling a different model variable. The two model variables are also displayed. Changing the selection of one radio group causes the indicator to disappear from the other radio group. > Two RadioGroups on one page interfering with one another > > > Key: WICKET-1601 > URL: https://issues.apache.org/jira/browse/WICKET-1601 > Project: Wicket > Issue Type: Bug >Affects Versions: 1.3.3 > Environment: generic >Reporter: Frank Silbermann > Attachments: myproject.zip > > > I created a simple Panel that contains a formatted RadioGroup with > wantOnSelectionChangedNotifications() returning true. (Its constructor > accepts an array of options, a PropertyModel to be controlled, and a caption > for the label.) I put two instances of this panel on a single page, each > controlling its own model variable. The page displays the two RadioGroup > panels and displays the value of the two model variables. > When I select a radiobutton from one group, all the radio buttons from the > other group become unselected (i.e., the dot indicator disappears) -- as > though the radio buttons belonged to the same button group. > My quickstart project illustrating the behavior (if I can figure out how to > attach it) uses Wicket 1.3.3. Bring up the home page and begin clicking its > radio groups to see the behavior. > I discovered this problem in my Wicket 1.2 application when I tried to > upgrade its libraries from Wicket 1.2.2 to Wicket 1.2.6. (With the new > libraries, I also began seeing a great many puzzling new null value errors.) > If the bug gets fixed in Wicket 1.3, I'll upgrade my application to it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (WICKET-1601) Two RadioGroups on one page interfering with one another
Two RadioGroups on one page interfering with one another Key: WICKET-1601 URL: https://issues.apache.org/jira/browse/WICKET-1601 Project: Wicket Issue Type: Bug Affects Versions: 1.3.3 Environment: generic Reporter: Frank Silbermann I created a simple Panel that contains a formatted RadioGroup with wantOnSelectionChangedNotifications() returning true. (Its constructor accepts an array of options, a PropertyModel to be controlled, and a caption for the label.) I put two instances of this panel on a single page, each controlling its own model variable. The page displays the two RadioGroup panels and displays the value of the two model variables. When I select a radiobutton from one group, all the radio buttons from the other group become unselected (i.e., the dot indicator disappears) -- as though the radio buttons belonged to the same button group. My quickstart project illustrating the behavior (if I can figure out how to attach it) uses Wicket 1.3.3. Bring up the home page and begin clicking its radio groups to see the behavior. I discovered this problem in my Wicket 1.2 application when I tried to upgrade its libraries from Wicket 1.2.2 to Wicket 1.2.6. (With the new libraries, I also began seeing a great many puzzling new null value errors.) If the bug gets fixed in Wicket 1.3, I'll upgrade my application to it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
