Re: [Wicket 1.3.3] Possible wicket:enclosure regression.
I just upgraded to 1.3.3 today and I'm having enclosure problems too -- it seems like their state isn't updated after the page is constructed. Is this fixed in trunk? Searched the list but haven't found anything yet. Thanks, Alex Fabio Fioretti wrote: Hi All, I'm experiencing a possible regression for wicket:enclosure in Wicket 1.3.3 (maybe related to the couple of patches that involved enclosures for 1.3.3). It thought of a regression because the following code works just fine in 1.3.1, even if I haven't tested it in 1.3.2. Basically, I have a RadioGroup with a couple of options. When the user selects the second option, a text field and link (wrapped in an enclosure) should appear next to the option. If she/he selects the first option, they should disappear again. Their visibility management is based on the enclosure. [snip] -- View this message in context: http://www.nabble.com/-Wicket-1.3.3--Possible-wicket%3Aenclosure-regression.-tp16480916p16991013.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Wicket 1.3.3] Possible wicket:enclosure regression.
Forget it, I found it in JIRA - says it's fixed for 1.4. Now I just need to find where to download it :) https://issues.apache.org/jira/browse/WICKET-1536 Alex On Apr 30, 2008, at 4:32 PM, Alex Jacoby wrote: I just upgraded to 1.3.3 today and I'm having enclosure problems too -- it seems like their state isn't updated after the page is constructed. Is this fixed in trunk? Searched the list but haven't found anything yet. Thanks, Alex Fabio Fioretti wrote: Hi All, I'm experiencing a possible regression for wicket:enclosure in Wicket 1.3.3 (maybe related to the couple of patches that involved enclosures for 1.3.3). It thought of a regression because the following code works just fine in 1.3.1, even if I haven't tested it in 1.3.2. Basically, I have a RadioGroup with a couple of options. When the user selects the second option, a text field and link (wrapped in an enclosure) should appear next to the option. If she/he selects the first option, they should disappear again. Their visibility management is based on the enclosure. [snip] -- View this message in context: http://www.nabble.com/-Wicket-1.3.3--Possible-wicket%3Aenclosure-regression.-tp16480916p16991013.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Wicket 1.3.3] Possible wicket:enclosure regression.
also fixed for 1.3.4... -igor On Wed, Apr 30, 2008 at 1:37 PM, Alex Jacoby [EMAIL PROTECTED] wrote: Forget it, I found it in JIRA - says it's fixed for 1.4. Now I just need to find where to download it :) https://issues.apache.org/jira/browse/WICKET-1536 Alex On Apr 30, 2008, at 4:32 PM, Alex Jacoby wrote: I just upgraded to 1.3.3 today and I'm having enclosure problems too -- it seems like their state isn't updated after the page is constructed. Is this fixed in trunk? Searched the list but haven't found anything yet. Thanks, Alex Fabio Fioretti wrote: Hi All, I'm experiencing a possible regression for wicket:enclosure in Wicket 1.3.3 (maybe related to the couple of patches that involved enclosures for 1.3.3). It thought of a regression because the following code works just fine in 1.3.1, even if I haven't tested it in 1.3.2. Basically, I have a RadioGroup with a couple of options. When the user selects the second option, a text field and link (wrapped in an enclosure) should appear next to the option. If she/he selects the first option, they should disappear again. Their visibility management is based on the enclosure. [snip] -- View this message in context: http://www.nabble.com/-Wicket-1.3.3--Possible-wicket%3Aenclosure-regression.-tp16480916p16991013.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Wicket 1.3.3] Possible wicket:enclosure regression.
Thanks. Is this the right place to download 1.3.4? http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-SNAPSHOT/ Cheers, Alex On Apr 30, 2008, at 4:45 PM, Igor Vaynberg wrote: also fixed for 1.3.4... -igor On Wed, Apr 30, 2008 at 1:37 PM, Alex Jacoby [EMAIL PROTECTED] wrote: Forget it, I found it in JIRA - says it's fixed for 1.4. Now I just need to find where to download it :) https://issues.apache.org/jira/browse/WICKET-1536 Alex On Apr 30, 2008, at 4:32 PM, Alex Jacoby wrote: I just upgraded to 1.3.3 today and I'm having enclosure problems too -- it seems like their state isn't updated after the page is constructed. Is this fixed in trunk? Searched the list but haven't found anything yet. Thanks, Alex Fabio Fioretti wrote: Hi All, I'm experiencing a possible regression for wicket:enclosure in Wicket 1.3.3 (maybe related to the couple of patches that involved enclosures for 1.3.3). It thought of a regression because the following code works just fine in 1.3.1, even if I haven't tested it in 1.3.2. Basically, I have a RadioGroup with a couple of options. When the user selects the second option, a text field and link (wrapped in an enclosure) should appear next to the option. If she/he selects the first option, they should disappear again. Their visibility management is based on the enclosure. [snip] -- View this message in context: http://www.nabble.com/-Wicket-1.3.3--Possible-wicket%3Aenclosure-regression.-tp16480916p16991013.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Wicket 1.3.3] Possible wicket:enclosure regression.
i think our bamboo instance might be having problems. so yes you can try there, if that snapshot is too old you can try checking out from source and mvn installing it -igor On Wed, Apr 30, 2008 at 1:50 PM, Alex Jacoby [EMAIL PROTECTED] wrote: Thanks. Is this the right place to download 1.3.4? http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-SNAPSHOT/ Cheers, Alex On Apr 30, 2008, at 4:45 PM, Igor Vaynberg wrote: also fixed for 1.3.4... -igor On Wed, Apr 30, 2008 at 1:37 PM, Alex Jacoby [EMAIL PROTECTED] wrote: Forget it, I found it in JIRA - says it's fixed for 1.4. Now I just need to find where to download it :) https://issues.apache.org/jira/browse/WICKET-1536 Alex On Apr 30, 2008, at 4:32 PM, Alex Jacoby wrote: I just upgraded to 1.3.3 today and I'm having enclosure problems too -- it seems like their state isn't updated after the page is constructed. Is this fixed in trunk? Searched the list but haven't found anything yet. Thanks, Alex Fabio Fioretti wrote: Hi All, I'm experiencing a possible regression for wicket:enclosure in Wicket 1.3.3 (maybe related to the couple of patches that involved enclosures for 1.3.3). It thought of a regression because the following code works just fine in 1.3.1, even if I haven't tested it in 1.3.2. Basically, I have a RadioGroup with a couple of options. When the user selects the second option, a text field and link (wrapped in an enclosure) should appear next to the option. If she/he selects the first option, they should disappear again. Their visibility management is based on the enclosure. [snip] -- View this message in context: http://www.nabble.com/-Wicket-1.3.3--Possible-wicket%3Aenclosure-regression.-tp16480916p16991013.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Wicket 1.3.3] Possible wicket:enclosure regression.
Hi All,
I'm experiencing a possible regression for wicket:enclosure in Wicket
1.3.3 (maybe related to the couple of patches that involved enclosures
for 1.3.3). It thought of a regression because the following code
works just fine in 1.3.1, even if I haven't tested it in 1.3.2.
Basically, I have a RadioGroup with a couple of options. When the user
selects the second option, a text field and link (wrapped in an
enclosure) should appear next to the option. If she/he selects the
first option, they should disappear again. Their visibility management
is based on the enclosure.
wicket:extend
form wicket:id=form
span wicket:id=radioGroup
input wicket:id=radioOne type=radio value=U
span onclick=event.cancelBubble = true;Set OPTION ONE
br/
/span
input wicket:id=radioTwo type=radio value=P/
span onclick=event.cancelBubble = true;Set OPTION TWO
wicket:enclosure child=textField
input wicket:id=textField type=text/
a wicket:id=linklink/a
/wicket:enclosure
br/
/span
/span
input type=button wicket:id=submitButton/
/form
/wicket:extend
On the Java side, the relevant code looks like this (feel free to ask
for further details):
radioGroup.add(new AjaxFormRadioUpdatingBehavior(onclick){
@Override
protected void onUpdate(AjaxRequestTarget target) {
if (OPTION_ONE.equals(getSelectedOption())) {
textField.setVisible(true);
} else {
textField.setVisible(false);
}
target.addComponent(radioGroup);
}
});
As you can see, I set the visibility of the textField depending on the
selected option and then update the container (the radioGroup). Again,
it worked fine in 1.3.1.
Is anybody aware of this or has anyone else experienced the same
change in enclosure functioning from Wicket 1.3.1 to 1.3.3?
Thank you very much and keep up the good work!
Fabio Fioretti - WindoM
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
