Re: 1.5 rc 4.2 ajax radiochoice bug?
hmm it does also occur when not using ajax.. 2011/5/30 nino martinez wael nino.martinez.w...@gmail.com: Hi Guys I've hit yet another possible bug. I'll fill in the jira if necessary heres how it is affecting our application. I have a form that has a propertylistview, in that list view theres a couple of different components where some are conditionally displayed depending on one of the formcomponents(componentA) which also has a ajaxformchoiceupdating behavior. If the radiochoice( componentB) starts by not being shown and then altered to get shown if the user clicks the right option on componentA, componentB gets redrawn by the ajaxupdate but then when the form are submitted I've debugged it and can see that somehow it's getting set to null instead of the selected choice. If componentB starts by being shown theres no problems... Hmm I probably need to provide a quickstart or are this sounding familiar to somebody? -N - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: 1.5 rc 4.2 ajax radiochoice bug?
Ok I have it replicated with a quickstart.. Seems the cause are because I am using an ldm in conjunction with the form is it wrong todo so? 2011/5/31 nino martinez wael nino.martinez.w...@gmail.com: hmm it does also occur when not using ajax.. 2011/5/30 nino martinez wael nino.martinez.w...@gmail.com: Hi Guys I've hit yet another possible bug. I'll fill in the jira if necessary heres how it is affecting our application. I have a form that has a propertylistview, in that list view theres a couple of different components where some are conditionally displayed depending on one of the formcomponents(componentA) which also has a ajaxformchoiceupdating behavior. If the radiochoice( componentB) starts by not being shown and then altered to get shown if the user clicks the right option on componentA, componentB gets redrawn by the ajaxupdate but then when the form are submitted I've debugged it and can see that somehow it's getting set to null instead of the selected choice. If componentB starts by being shown theres no problems... Hmm I probably need to provide a quickstart or are this sounding familiar to somebody? -N - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: 1.5 rc 4.2 ajax radiochoice bug?
Hi, using in cojuction with the ldm should be fine. On Tue, May 31, 2011 at 8:15 AM, nino martinez wael nino.martinez.w...@gmail.com wrote: Ok I have it replicated with a quickstart.. Seems the cause are because I am using an ldm in conjunction with the form is it wrong todo so? 2011/5/31 nino martinez wael nino.martinez.w...@gmail.com: hmm it does also occur when not using ajax.. 2011/5/30 nino martinez wael nino.martinez.w...@gmail.com: Hi Guys I've hit yet another possible bug. I'll fill in the jira if necessary heres how it is affecting our application. I have a form that has a propertylistview, in that list view theres a couple of different components where some are conditionally displayed depending on one of the formcomponents(componentA) which also has a ajaxformchoiceupdating behavior. If the radiochoice( componentB) starts by not being shown and then altered to get shown if the user clicks the right option on componentA, componentB gets redrawn by the ajaxupdate but then when the form are submitted I've debugged it and can see that somehow it's getting set to null instead of the selected choice. If componentB starts by being shown theres no problems... Hmm I probably need to provide a quickstart or are this sounding familiar to somebody? -N - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Pedro Henrique Oliveira dos Santos - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: 1.5 rc 4.2 ajax radiochoice bug?
just created this: https://issues.apache.org/jira/browse/WICKET-3756 2011/5/31 Pedro Santos pedros...@gmail.com: Hi, using in cojuction with the ldm should be fine. On Tue, May 31, 2011 at 8:15 AM, nino martinez wael nino.martinez.w...@gmail.com wrote: Ok I have it replicated with a quickstart.. Seems the cause are because I am using an ldm in conjunction with the form is it wrong todo so? 2011/5/31 nino martinez wael nino.martinez.w...@gmail.com: hmm it does also occur when not using ajax.. 2011/5/30 nino martinez wael nino.martinez.w...@gmail.com: Hi Guys I've hit yet another possible bug. I'll fill in the jira if necessary heres how it is affecting our application. I have a form that has a propertylistview, in that list view theres a couple of different components where some are conditionally displayed depending on one of the formcomponents(componentA) which also has a ajaxformchoiceupdating behavior. If the radiochoice( componentB) starts by not being shown and then altered to get shown if the user clicks the right option on componentA, componentB gets redrawn by the ajaxupdate but then when the form are submitted I've debugged it and can see that somehow it's getting set to null instead of the selected choice. If componentB starts by being shown theres no problems... Hmm I probably need to provide a quickstart or are this sounding familiar to somebody? -N - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Pedro Henrique Oliveira dos Santos - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
