You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Frank Silbermann <fr...@fedex.com> on 2008/05/08 19:06:00 UTC
Bug introduced somewhere after 1.2.2 is still in 1.3.3
I wrote earlier about my problems going from Wicket 1.2.2 to Wicket
1.2.6. This has to do with a RadioGroup component that I built;
whenever I used it on more than one page, clicking on one RadioGroup
caused the marker to disapper from all the other RadioGroups on the
page.
I wasn't given much help because Wicket 1.2 is end-of-life. Today I
tried the example on Wicked 1.3.3. I downloaded the QuickStart
application for Wicket 1.3.3, installed an upgraded version of my
RadioGroup component, modified the home page to show my RadioGroup panel
twice, and the bad behavior is still there.
By the way, the only change in the generated HTML that I could see was
that in Wicket 1.2.2 the buttons were defined:
<input value="radios:2:radio" ...etc.
-- with the numbers starting over again for each RadioGroup, whereas in
Wicket 1.2.6 and Wicket 1.3.3 it was more like:
<input value="radio7" ...etc.
with the numbers _not_ starting over for each RadioGroup. Clicking on
one radio group causes the marker to disappear from the other radio
group -- as if part of Wicket were treating the buttons as though they
all belonged to the same radio group.
I'd like the Wicket 1.3 developers either to fix the bug in a future
release (after which I'll upgrade my entire application to 1.3), or tell
me what I'm doing wrong. How do I get the process started?
/Frank
-----Original Message-----
From: Johan Compagner [mailto:jcompagner@gmail.com]
Sent: Tuesday, April 29, 2008 12:31 PM
To: users@wicket.apache.org
Subject: Re: Change to API between Wicket 1.2 releases?
I dont know what this is, but 1.2 is pretty much end of life, so you
should try to debug what it is and patch your version Or just use a 1.2
version that works for you
On 4/29/08, Frank Silbermann <fr...@fedex.com> wrote:
> I'm not sure what you mean by "what part it really is"? Are you
> asking me to find a simpler example exhibiting the problem? I mean,
> the panel class follows the RadioGroup component example quite
closely:
>
> http://wicketstuff.org/wicket13/compref/;jsessionid=C6F7701B6426601795
> 63
> 84008732211C?wicket:bookmarkablePage=%3Aorg.apache.wicket.examples.com
> pr
> ef.RadioGroupPage
>
> The only significant difference is that instead of using a submit
> button I override wantOnSelectionChangedNotification() to return true.
>
> public class MyPanel extends Panel {
>
> public MyPanel( String id,
> String caption,
> PropertyModel groupModel,
> ChoiceOption[] options ) {
>
> super(id, groupModel);
>
> add( new Label("caption", caption) );
>
> final RadioGroup group = new RadioGroup("group", groupModel)
{
> // THIS IS THE ONLY PART THAT CHANGED FROM THE
> COMPONENT EXAMPLE
> protected boolean
> wantOnSelectionChangedNotifications()
> {
> return true;
> }
> // IT POSTS BACK ON ANY SELECTION
> };
> add(group);
>
> List<ChoiceOption> optionList = Arrays.asList( options );
>
> ListView radios = new ListView("radios", optionList) {
> protected void populateItem(ListItem listItem) {
> listItem.add( new Radio("radio",
> new PropertyModel(
> listItem.getModel(),
> "value")
> )
> );
> listItem.add( new Label("option",
> new PropertyModel(
> listItem.getModel(), "label" )
> )
> );
> }
> };
>
> group.add(radios);
> }
>
> Did I do something wrong, or is that feature of RadioGroup indeed
> broken in current releases of Wicket 1.2?
>
> I really don't know enough about the Wicket internals to debug Wicket.
> Can you suggest anything simpler that I could try to narrow down the
> location of the problem? Would it work in Wicket 1.3?
>
>
> -----Original Message-----
> From: Johan Compagner [mailto:jcompagner@gmail.com]
> Sent: Tuesday, April 29, 2008 3:54 AM
> To: users@wicket.apache.org
> Subject: Re: Change to API between Wicket 1.2 releases?
>
> 1.2 is a long time ago
> I have no idea what change did break yours (and what did it fix) If
> you could figure out what part it really is?
>
> johan
>
>
> On Tue, Apr 29, 2008 at 12:09 AM, Frank Silbermann <
> frank.silbermann@fedex.com> wrote:
>
> > I completed a Wicket 1.2 project a couple of years ago, and I've
> > been maintaining it since then. I've been using Version 1.2.2
> > successfully,
>
> > and figured I might as well use the lastest release of that version
> > (1.2.7). Well, I'm trying to figure out why Wicket 1.2.7 broke my
> code.
> > (I scrounged up a Wicket 1.2.6 release, and that also breaks it.)
> >
> > Am I using the Wicket 1.2 API incorrectly? When it works in Wicket
> > 1.2.2, am I using it in an unintended way? Let me illustrate what
> > I've been doing with a small example.
> >
> > This is a simplified version of a component for creating and
> > displaying radio button groups without having to write HTML every
> > time. I give the
> > constructor:
> >
> > (1) a wicket-id,
> >
> > (2) a PropertyModel that initializes the component and keeps track
> > of the current choice, and
> >
> > (3) an array of ChoiceOption. -- The array of choice options
> > defines the set of values offered by the radio buttons, and the
> > corresponding labels to be displayed.
> >
> > The component posts back immediately when a change is made to the
> > radio button. (Think fast INTRAnet with a very small number of
> > simulaneous
> > users.) Here is my implementation:
> >
> > package common.play;
> >
> > import wicket.markup.html.basic.Label; import wicket.model.IModel;
> > import wicket.markup.html.panel.Panel; import
> > wicket.markup.html.form.Radio; import
> > wicket.markup.html.form.RadioGroup;
> > import wicket.markup.html.list.ListItem; import
> > wicket.markup.html.list.ListView; import wicket.model.PropertyModel;
> > import java.util.List; import java.util.Arrays; import
> > common.play.ChoiceOption;
> >
> > public class MyPanel extends Panel {
> >
> > public MyPanel( String id, String caption, PropertyModel
> > groupModel, ChoiceOption[] options) {
> > super(id, groupModel);
> >
> > add( new Label("caption", caption) );
> > final RadioGroup group = new RadioGroup("group", groupModel) {
> > protected boolean wantOnSelectionChangedNotifications() {
> > return
> true; }
> > };
> > add(group);
> >
> > List<ChoiceOption> optionList = Arrays.asList( options );
> > ListView radios = new ListView("radios", optionList) {
> > protected void populateItem(ListItem listItem) {
> > listItem.add( new Radio("radio",
> > new PropertyModel(
> > listItem.getModel(),
> > "value") ) );
> > listItem.add( new Label("option", new PropertyModel(
> > listItem.getModel(), "label" )));
> > }
> > };
> >
> > group.add(radios);
> > }
> >
> > ----------------------------------------------------------------
> >
> > package common.play;
> >
> > public class ChoiceOption implements java.io.Serializable { public
> > String value; public String label;
> >
> > public ChoiceOption(String value, String label) {
> > this.value = value;
> > this.label = label;
> > }
> > }
> >
> > --------------------------------------------------------------------
> > --
> > --
> > ------------------------
> >
> > This is the layout for displaying my component. It's a divided box
> > that puts the group caption in one half, and in the other half
> > provides the set of labeled buttons. Note that I'm using a
> > ListView, because each usage may require a different number of
choices.
> >
> > <html xmlns="http://www.w3.org/1999/xhtml
> > <http://www.w3.org/1999/xhtml> "
> > xmlns:wicket="http://wicket.sourceforge.net/
> > <http://wicket.sourceforge.net/> " xml:lang="en" lang="en"> <head>
> > <link rel="stylesheet" type="text/css" href="style.css"/> </head>
> > <body> <wicket:panel> <table border=1>
> > <tr>
> > <td>
> > <span wicket:id="caption">Caption</span>
> > </td>
> > <td>
> > <span wicket:id="group">
> > <table cellpadding=5>
> > <tr>
> > <td wicket:id="radios" align="center">
> > <input type="radio" wicket:id="radio"/>
> > <span wicket:id="option">option name</span>
> >
> > </td>
> > </tr>
> > </table>
> > </span>
> > </td>
> > </tr>
> > </table>
> > </wicket:panel>
> > </body>
> > </html>
> >
> >
> > Here is a page with two intances of this component; one set of radio
> > buttons below the other, within a form. Below my form are two
> > labels, one below the other, which indicate the value currently
> > chosen by the corresponding radio-button set.
> >
> > import wicket.markup.html.WebPage;
> > import wicket.markup.html.panel.Panel; import
> > wicket.markup.html.form.Form; import wicket.model.PropertyModel;
> > import wicket.markup.html.basic.Label; import
> > common.play.ChoiceOption;
> >
> > public class MyPage extends WebPage {
> >
> > public String firstProperty = "A";
> > public String secondProperty = "A";
> >
> > ChoiceOption[] options = { new ChoiceOption("A", "Ay"),
> > new ChoiceOption("B", "Bee"),
> > new ChoiceOption("C", "See"),
> > new ChoiceOption("D", "Dee") };
> >
> > public MyPage() {
> >
> > Form form = new Form("form");
> > add( form );
> >
> > Panel panel1 = new MyPanel( "panel1",
> > "1st choice",
> > new PropertyModel( this,
> > "firstProperty"),
> > options
> > );
> > form.add( panel1 );
> >
> >
> > Panel panel2 = new MyPanel( "panel2",
> > "2nd choice",
> > new PropertyModel( this,
> > "secondProperty"),
> > options
> > );
> > form.add( panel2 );
> >
> > add( new Label( "result1",
> > new PropertyModel(this, "firstProperty")
> > )
> > );
> >
> > add( new Label( "result2",
> > new PropertyModel( this, "secondProperty")
> > )
> > );
> > }
> > }
> >
> >
> > <html xmlns="http://www.w3.org/1999/xhtml
> <http://www.w3.org/1999/xhtml>
> > " xmlns:wicket="http://wicket.sourceforge.net/
> > <http://wicket.sourceforge.net/> " xml:lang="en" lang="en"> <head>
> > <link rel="stylesheet" type="text/css" href="style.css"/> </head>
> > <body> <form wicket:id="form" id="form" name="form"> <span
> > wicket:id="panel1"> first radiobutton set appears here </span>
> > <span wicket:id="panel2"> second radiobutton set appears here
> > </span> </form> <div wicket:id="result1"> first selected choice
> > appears here</div> <div wicket:id="result2">second selected choice
> > appears here</div> </body> </html>
> >
> > This works just fine in Wicket 1.2.2, but when I use Wicket 1.2.6
> > or Wicket 1.2.7, I find that when I move the black dot by selecting
> another
> > choice in one group, the black dot in the other group disappears.
> > Sometimes both dots disappear.I play with the radio buttons the
> > black dot disappears, even though the model for each button group
> > maintains the proper value.
> >
> > The disappearance of the indicator dot is merely the most obvious
> > manifestation of the problem. By application is crashing like crazy
> > with Wicket 1.2.7, but works just fine with Wicket 1.2.2.
> >
> > Am I using the Wicket 1.2 API incorrectly? Is there some problem
> > with my use of ListView, or PropertyModel? When it works in Wicket
> > 1.2.2,
> am
> > I taking advantage of undocumented behavior? What am I
> > misunderstanding? If this is the result of a change that was made
> > for improved AJAX support, what would be my simplest work-around?
> >
> > /Frank
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
Posted by Per Newgro <pe...@gmx.ch>.
Hello Frank Silbermann:
> Well, then, as I am a beginner who hasn't worked much with open source,
> could you please point me to a reference that explains what a jira issue
> is and how to create one? (I'm guessing that it's an entry into some
> sort of bug tracking database.)
Sure you can. You could use the mailing list search at nabble.com because the
question was asked and answered once a month :-)
Use http://issues.apache.org/jira/browse/ - goto wicket - login (you have to
get an account) - press new issue and follow instructions.
Its realy easy and helps alot to stay in touch with the open issues.
>
> Also, by "attaching a quickstart Project" do you mean simply a zipped
> archive of a project directory that was created by installing the
> quickstart project and minimally modifying it to create a web
> application that exhibits the bug?
Yes.
Cheers
Per
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Bug introduced somewhere after 1.2.2 is still in 1.3.3
Posted by Frank Silbermann <fr...@fedex.com>.
Well, then, as I am a beginner who hasn't worked much with open source,
could you please point me to a reference that explains what a jira issue
is and how to create one? (I'm guessing that it's an entry into some
sort of bug tracking database.)
Also, by "attaching a quickstart Project" do you mean simply a zipped
archive of a project directory that was created by installing the
quickstart project and minimally modifying it to create a web
application that exhibits the bug?
-----Original Message-----
From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
Sent: Thursday, May 08, 2008 12:13 PM
To: users@wicket.apache.org
Subject: Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
On Thu, May 8, 2008 at 10:06 AM, Frank Silbermann
<fr...@fedex.com> wrote:
> I wrote earlier about my problems going from Wicket 1.2.2 to Wicket
> 1.2.6. This has to do with a RadioGroup component that I built;
> whenever I used it on more than one page, clicking on one RadioGroup
> caused the marker to disapper from all the other RadioGroups on the
> page.
>
> I wasn't given much help because Wicket 1.2 is end-of-life. Today I
> tried the example on Wicked 1.3.3. I downloaded the QuickStart
> application for Wicket 1.3.3, installed an upgraded version of my
> RadioGroup component, modified the home page to show my RadioGroup
> panel twice, and the bad behavior is still there.
>
> By the way, the only change in the generated HTML that I could see
> was that in Wicket 1.2.2 the buttons were defined:
>
> <input value="radios:2:radio" ...etc.
>
> -- with the numbers starting over again for each RadioGroup, whereas
> in Wicket 1.2.6 and Wicket 1.3.3 it was more like:
>
> <input value="radio7" ...etc.
>
> with the numbers _not_ starting over for each RadioGroup. Clicking
> on one radio group causes the marker to disappear from the other
> radio group -- as if part of Wicket were treating the buttons as
> though they all belonged to the same radio group.
>
> I'd like the Wicket 1.3 developers either to fix the bug in a future
> release (after which I'll upgrade my entire application to 1.3), or
> tell me what I'm doing wrong. How do I get the process started?
the usual way, create a jira issue and attach a quickstart project that
demonstrates the problem. than post the jira url back into this thread.
it is not very helpful when you post huge fragments of code and markup
into an email.
-igor
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Bug introduced somewhere after 1.2.2 is still in 1.3.3
Posted by Frank Silbermann <fr...@fedex.com>.
I added https://issues.apache.org/jira/browse/WICKET-1621 to say that
the Component Example for RadioGroup, which contains a ListView of Form
components, ought to call #setReuseItems(true).
The example as written works, of course, but not when I put two such
RadioGroups on the page. A person who adapts the examples without
reading the JavaDoc can get into trouble, as I did.
/Frank
-----Original Message-----
From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
Sent: Friday, May 09, 2008 12:52 PM
To: users@wicket.apache.org
Subject: Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
call setReuseItems(true) on the listview that contains radio components.
javadoc of listview recommends this for listviews inside forms that
contain formcomponents.
-igor
On Thu, May 8, 2008 at 1:49 PM, Frank Silbermann
<fr...@fedex.com> wrote:
> Here's the URL of my jira issue.
>
> https://issues.apache.org/jira/browse/WICKET-1601
>
> The issue has attached a quickstart project and a screen print.
>
> -----Original Message-----
> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> Sent: Thursday, May 08, 2008 12:13 PM
> To: users@wicket.apache.org
> Subject: Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
>
> On Thu, May 8, 2008 at 10:06 AM, Frank Silbermann
> <fr...@fedex.com> wrote:
>> I wrote earlier about my problems going from Wicket 1.2.2 to Wicket
>> 1.2.6. This has to do with a RadioGroup component that I built;
>> whenever I used it on more than one page, clicking on one RadioGroup
>> caused the marker to disapper from all the other RadioGroups on the
>> page.
>>
>> I wasn't given much help because Wicket 1.2 is end-of-life. Today I
>
>> tried the example on Wicked 1.3.3. I downloaded the QuickStart
>> application for Wicket 1.3.3, installed an upgraded version of my
>> RadioGroup component, modified the home page to show my RadioGroup
>> panel twice, and the bad behavior is still there.
>>
>> By the way, the only change in the generated HTML that I could see
>> was that in Wicket 1.2.2 the buttons were defined:
>>
>> <input value="radios:2:radio" ...etc.
>>
>> -- with the numbers starting over again for each RadioGroup, whereas
>> in Wicket 1.2.6 and Wicket 1.3.3 it was more like:
>>
>> <input value="radio7" ...etc.
>>
>> with the numbers _not_ starting over for each RadioGroup. Clicking
>> on one radio group causes the marker to disappear from the other
>> radio group -- as if part of Wicket were treating the buttons as
>> though they all belonged to the same radio group.
>>
>> I'd like the Wicket 1.3 developers either to fix the bug in a future
>
>> release (after which I'll upgrade my entire application to 1.3), or
>> tell me what I'm doing wrong. How do I get the process started?
>
> the usual way, create a jira issue and attach a quickstart project
> that demonstrates the problem. than post the jira url back into this
thread.
> it is not very helpful when you post huge fragments of code and markup
> into an email.
>
> -igor
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
Posted by Igor Vaynberg <ig...@gmail.com>.
this only mainly affects components that recreate hierarchies - eg
repeaters. refreshingview has an iitemreusestrategy you would have to
set.
-igor
On Fri, May 9, 2008 at 11:50 AM, Frank Silbermann
<fr...@fedex.com> wrote:
> I can search my application for ListView occuring in a form and do this.
> Are there any other components that require something like this when
> used in a Form? E.g. in Wicket Extensions?
>
> -----Original Message-----
> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> Sent: Friday, May 09, 2008 12:52 PM
> To: users@wicket.apache.org
> Subject: Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
>
> call setReuseItems(true) on the listview that contains radio components.
> javadoc of listview recommends this for listviews inside forms that
> contain formcomponents.
>
> -igor
>
>
> On Thu, May 8, 2008 at 1:49 PM, Frank Silbermann
> <fr...@fedex.com> wrote:
>> Here's the URL of my jira issue.
>>
>> https://issues.apache.org/jira/browse/WICKET-1601
>>
>> The issue has attached a quickstart project and a screen print.
>>
>> -----Original Message-----
>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>> Sent: Thursday, May 08, 2008 12:13 PM
>> To: users@wicket.apache.org
>> Subject: Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
>>
>> On Thu, May 8, 2008 at 10:06 AM, Frank Silbermann
>> <fr...@fedex.com> wrote:
>>> I wrote earlier about my problems going from Wicket 1.2.2 to Wicket
>>> 1.2.6. This has to do with a RadioGroup component that I built;
>>> whenever I used it on more than one page, clicking on one RadioGroup
>>> caused the marker to disapper from all the other RadioGroups on the
>>> page.
>>>
>>> I wasn't given much help because Wicket 1.2 is end-of-life. Today I
>>
>>> tried the example on Wicked 1.3.3. I downloaded the QuickStart
>>> application for Wicket 1.3.3, installed an upgraded version of my
>>> RadioGroup component, modified the home page to show my RadioGroup
>>> panel twice, and the bad behavior is still there.
>>>
>>> By the way, the only change in the generated HTML that I could see
>>> was that in Wicket 1.2.2 the buttons were defined:
>>>
>>> <input value="radios:2:radio" ...etc.
>>>
>>> -- with the numbers starting over again for each RadioGroup, whereas
>
>>> in Wicket 1.2.6 and Wicket 1.3.3 it was more like:
>>>
>>> <input value="radio7" ...etc.
>>>
>>> with the numbers _not_ starting over for each RadioGroup. Clicking
>>> on one radio group causes the marker to disappear from the other
>>> radio group -- as if part of Wicket were treating the buttons as
>>> though they all belonged to the same radio group.
>>>
>>> I'd like the Wicket 1.3 developers either to fix the bug in a future
>>
>>> release (after which I'll upgrade my entire application to 1.3), or
>>> tell me what I'm doing wrong. How do I get the process started?
>>
>> the usual way, create a jira issue and attach a quickstart project
>> that demonstrates the problem. than post the jira url back into this
> thread.
>> it is not very helpful when you post huge fragments of code and markup
>
>> into an email.
>>
>> -igor
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Bug introduced somewhere after 1.2.2 is still in 1.3.3
Posted by Frank Silbermann <fr...@fedex.com>.
I can search my application for ListView occuring in a form and do this.
Are there any other components that require something like this when
used in a Form? E.g. in Wicket Extensions?
-----Original Message-----
From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
Sent: Friday, May 09, 2008 12:52 PM
To: users@wicket.apache.org
Subject: Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
call setReuseItems(true) on the listview that contains radio components.
javadoc of listview recommends this for listviews inside forms that
contain formcomponents.
-igor
On Thu, May 8, 2008 at 1:49 PM, Frank Silbermann
<fr...@fedex.com> wrote:
> Here's the URL of my jira issue.
>
> https://issues.apache.org/jira/browse/WICKET-1601
>
> The issue has attached a quickstart project and a screen print.
>
> -----Original Message-----
> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> Sent: Thursday, May 08, 2008 12:13 PM
> To: users@wicket.apache.org
> Subject: Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
>
> On Thu, May 8, 2008 at 10:06 AM, Frank Silbermann
> <fr...@fedex.com> wrote:
>> I wrote earlier about my problems going from Wicket 1.2.2 to Wicket
>> 1.2.6. This has to do with a RadioGroup component that I built;
>> whenever I used it on more than one page, clicking on one RadioGroup
>> caused the marker to disapper from all the other RadioGroups on the
>> page.
>>
>> I wasn't given much help because Wicket 1.2 is end-of-life. Today I
>
>> tried the example on Wicked 1.3.3. I downloaded the QuickStart
>> application for Wicket 1.3.3, installed an upgraded version of my
>> RadioGroup component, modified the home page to show my RadioGroup
>> panel twice, and the bad behavior is still there.
>>
>> By the way, the only change in the generated HTML that I could see
>> was that in Wicket 1.2.2 the buttons were defined:
>>
>> <input value="radios:2:radio" ...etc.
>>
>> -- with the numbers starting over again for each RadioGroup, whereas
>> in Wicket 1.2.6 and Wicket 1.3.3 it was more like:
>>
>> <input value="radio7" ...etc.
>>
>> with the numbers _not_ starting over for each RadioGroup. Clicking
>> on one radio group causes the marker to disappear from the other
>> radio group -- as if part of Wicket were treating the buttons as
>> though they all belonged to the same radio group.
>>
>> I'd like the Wicket 1.3 developers either to fix the bug in a future
>
>> release (after which I'll upgrade my entire application to 1.3), or
>> tell me what I'm doing wrong. How do I get the process started?
>
> the usual way, create a jira issue and attach a quickstart project
> that demonstrates the problem. than post the jira url back into this
thread.
> it is not very helpful when you post huge fragments of code and markup
> into an email.
>
> -igor
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
Posted by Igor Vaynberg <ig...@gmail.com>.
too much magic imho
-igor
On Fri, May 9, 2008 at 11:57 AM, Johan Compagner <jc...@gmail.com> wrote:
> we could make this automatic?
> search for a parent that is a Form?
>
> johan
>
>
> On Fri, May 9, 2008 at 7:52 PM, Igor Vaynberg <ig...@gmail.com>
> wrote:
>
>> call setReuseItems(true) on the listview that contains radio
>> components. javadoc of listview recommends this for listviews inside
>> forms that contain formcomponents.
>>
>> -igor
>>
>>
>> On Thu, May 8, 2008 at 1:49 PM, Frank Silbermann
>> <fr...@fedex.com> wrote:
>> > Here's the URL of my jira issue.
>> >
>> > https://issues.apache.org/jira/browse/WICKET-1601
>> >
>> > The issue has attached a quickstart project and a screen print.
>> >
>> > -----Original Message-----
>> > From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>> > Sent: Thursday, May 08, 2008 12:13 PM
>> > To: users@wicket.apache.org
>> > Subject: Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
>> >
>> > On Thu, May 8, 2008 at 10:06 AM, Frank Silbermann
>> > <fr...@fedex.com> wrote:
>> >> I wrote earlier about my problems going from Wicket 1.2.2 to Wicket
>> >> 1.2.6. This has to do with a RadioGroup component that I built;
>> >> whenever I used it on more than one page, clicking on one RadioGroup
>> >> caused the marker to disapper from all the other RadioGroups on the
>> >> page.
>> >>
>> >> I wasn't given much help because Wicket 1.2 is end-of-life. Today I
>> >
>> >> tried the example on Wicked 1.3.3. I downloaded the QuickStart
>> >> application for Wicket 1.3.3, installed an upgraded version of my
>> >> RadioGroup component, modified the home page to show my RadioGroup
>> >> panel twice, and the bad behavior is still there.
>> >>
>> >> By the way, the only change in the generated HTML that I could see
>> >> was that in Wicket 1.2.2 the buttons were defined:
>> >>
>> >> <input value="radios:2:radio" ...etc.
>> >>
>> >> -- with the numbers starting over again for each RadioGroup, whereas
>> >> in Wicket 1.2.6 and Wicket 1.3.3 it was more like:
>> >>
>> >> <input value="radio7" ...etc.
>> >>
>> >> with the numbers _not_ starting over for each RadioGroup. Clicking
>> >> on one radio group causes the marker to disappear from the other
>> >> radio group -- as if part of Wicket were treating the buttons as
>> >> though they all belonged to the same radio group.
>> >>
>> >> I'd like the Wicket 1.3 developers either to fix the bug in a future
>> >
>> >> release (after which I'll upgrade my entire application to 1.3), or
>> >> tell me what I'm doing wrong. How do I get the process started?
>> >
>> > the usual way, create a jira issue and attach a quickstart project that
>> > demonstrates the problem. than post the jira url back into this thread.
>> > it is not very helpful when you post huge fragments of code and markup
>> > into an email.
>> >
>> > -igor
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> > For additional commands, e-mail: users-help@wicket.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Bug introduced somewhere after 1.2.2 is still in 1.3.3
Posted by Frank Silbermann <fr...@fedex.com>.
That sounds convenient. But what if someone wants his Form to contain a
ListView that _doesn't_ contain form components?
-----Original Message-----
From: Johan Compagner [mailto:jcompagner@gmail.com]
Sent: Friday, May 09, 2008 1:57 PM
To: users@wicket.apache.org
Subject: Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
we could make this automatic?
search for a parent that is a Form?
johan
On Fri, May 9, 2008 at 7:52 PM, Igor Vaynberg <ig...@gmail.com>
wrote:
> call setReuseItems(true) on the listview that contains radio
> components. javadoc of listview recommends this for listviews inside
> forms that contain formcomponents.
>
> -igor
>
>
> On Thu, May 8, 2008 at 1:49 PM, Frank Silbermann
> <fr...@fedex.com> wrote:
> > Here's the URL of my jira issue.
> >
> > https://issues.apache.org/jira/browse/WICKET-1601
> >
> > The issue has attached a quickstart project and a screen print.
> >
> > -----Original Message-----
> > From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> > Sent: Thursday, May 08, 2008 12:13 PM
> > To: users@wicket.apache.org
> > Subject: Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
> >
> > On Thu, May 8, 2008 at 10:06 AM, Frank Silbermann
> > <fr...@fedex.com> wrote:
> >> I wrote earlier about my problems going from Wicket 1.2.2 to Wicket
> >> 1.2.6. This has to do with a RadioGroup component that I built;
> >> whenever I used it on more than one page, clicking on one
> >> RadioGroup caused the marker to disapper from all the other
> >> RadioGroups on the page.
> >>
> >> I wasn't given much help because Wicket 1.2 is end-of-life. Today
> >> I
> >
> >> tried the example on Wicked 1.3.3. I downloaded the QuickStart
> >> application for Wicket 1.3.3, installed an upgraded version of my
> >> RadioGroup component, modified the home page to show my RadioGroup
> >> panel twice, and the bad behavior is still there.
> >>
> >> By the way, the only change in the generated HTML that I could see
> >> was that in Wicket 1.2.2 the buttons were defined:
> >>
> >> <input value="radios:2:radio" ...etc.
> >>
> >> -- with the numbers starting over again for each RadioGroup,
> >> whereas in Wicket 1.2.6 and Wicket 1.3.3 it was more like:
> >>
> >> <input value="radio7" ...etc.
> >>
> >> with the numbers _not_ starting over for each RadioGroup.
> >> Clicking on one radio group causes the marker to disappear from
> >> the other radio group -- as if part of Wicket were treating the
> >> buttons as though they all belonged to the same radio group.
> >>
> >> I'd like the Wicket 1.3 developers either to fix the bug in a
> >> future
> >
> >> release (after which I'll upgrade my entire application to 1.3), or
> >> tell me what I'm doing wrong. How do I get the process started?
> >
> > the usual way, create a jira issue and attach a quickstart project
> > that demonstrates the problem. than post the jira url back into this
thread.
> > it is not very helpful when you post huge fragments of code and
> > markup into an email.
> >
> > -igor
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
Posted by Johan Compagner <jc...@gmail.com>.
we could make this automatic?
search for a parent that is a Form?
johan
On Fri, May 9, 2008 at 7:52 PM, Igor Vaynberg <ig...@gmail.com>
wrote:
> call setReuseItems(true) on the listview that contains radio
> components. javadoc of listview recommends this for listviews inside
> forms that contain formcomponents.
>
> -igor
>
>
> On Thu, May 8, 2008 at 1:49 PM, Frank Silbermann
> <fr...@fedex.com> wrote:
> > Here's the URL of my jira issue.
> >
> > https://issues.apache.org/jira/browse/WICKET-1601
> >
> > The issue has attached a quickstart project and a screen print.
> >
> > -----Original Message-----
> > From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> > Sent: Thursday, May 08, 2008 12:13 PM
> > To: users@wicket.apache.org
> > Subject: Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
> >
> > On Thu, May 8, 2008 at 10:06 AM, Frank Silbermann
> > <fr...@fedex.com> wrote:
> >> I wrote earlier about my problems going from Wicket 1.2.2 to Wicket
> >> 1.2.6. This has to do with a RadioGroup component that I built;
> >> whenever I used it on more than one page, clicking on one RadioGroup
> >> caused the marker to disapper from all the other RadioGroups on the
> >> page.
> >>
> >> I wasn't given much help because Wicket 1.2 is end-of-life. Today I
> >
> >> tried the example on Wicked 1.3.3. I downloaded the QuickStart
> >> application for Wicket 1.3.3, installed an upgraded version of my
> >> RadioGroup component, modified the home page to show my RadioGroup
> >> panel twice, and the bad behavior is still there.
> >>
> >> By the way, the only change in the generated HTML that I could see
> >> was that in Wicket 1.2.2 the buttons were defined:
> >>
> >> <input value="radios:2:radio" ...etc.
> >>
> >> -- with the numbers starting over again for each RadioGroup, whereas
> >> in Wicket 1.2.6 and Wicket 1.3.3 it was more like:
> >>
> >> <input value="radio7" ...etc.
> >>
> >> with the numbers _not_ starting over for each RadioGroup. Clicking
> >> on one radio group causes the marker to disappear from the other
> >> radio group -- as if part of Wicket were treating the buttons as
> >> though they all belonged to the same radio group.
> >>
> >> I'd like the Wicket 1.3 developers either to fix the bug in a future
> >
> >> release (after which I'll upgrade my entire application to 1.3), or
> >> tell me what I'm doing wrong. How do I get the process started?
> >
> > the usual way, create a jira issue and attach a quickstart project that
> > demonstrates the problem. than post the jira url back into this thread.
> > it is not very helpful when you post huge fragments of code and markup
> > into an email.
> >
> > -igor
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
Posted by Igor Vaynberg <ig...@gmail.com>.
call setReuseItems(true) on the listview that contains radio
components. javadoc of listview recommends this for listviews inside
forms that contain formcomponents.
-igor
On Thu, May 8, 2008 at 1:49 PM, Frank Silbermann
<fr...@fedex.com> wrote:
> Here's the URL of my jira issue.
>
> https://issues.apache.org/jira/browse/WICKET-1601
>
> The issue has attached a quickstart project and a screen print.
>
> -----Original Message-----
> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> Sent: Thursday, May 08, 2008 12:13 PM
> To: users@wicket.apache.org
> Subject: Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
>
> On Thu, May 8, 2008 at 10:06 AM, Frank Silbermann
> <fr...@fedex.com> wrote:
>> I wrote earlier about my problems going from Wicket 1.2.2 to Wicket
>> 1.2.6. This has to do with a RadioGroup component that I built;
>> whenever I used it on more than one page, clicking on one RadioGroup
>> caused the marker to disapper from all the other RadioGroups on the
>> page.
>>
>> I wasn't given much help because Wicket 1.2 is end-of-life. Today I
>
>> tried the example on Wicked 1.3.3. I downloaded the QuickStart
>> application for Wicket 1.3.3, installed an upgraded version of my
>> RadioGroup component, modified the home page to show my RadioGroup
>> panel twice, and the bad behavior is still there.
>>
>> By the way, the only change in the generated HTML that I could see
>> was that in Wicket 1.2.2 the buttons were defined:
>>
>> <input value="radios:2:radio" ...etc.
>>
>> -- with the numbers starting over again for each RadioGroup, whereas
>> in Wicket 1.2.6 and Wicket 1.3.3 it was more like:
>>
>> <input value="radio7" ...etc.
>>
>> with the numbers _not_ starting over for each RadioGroup. Clicking
>> on one radio group causes the marker to disappear from the other
>> radio group -- as if part of Wicket were treating the buttons as
>> though they all belonged to the same radio group.
>>
>> I'd like the Wicket 1.3 developers either to fix the bug in a future
>
>> release (after which I'll upgrade my entire application to 1.3), or
>> tell me what I'm doing wrong. How do I get the process started?
>
> the usual way, create a jira issue and attach a quickstart project that
> demonstrates the problem. than post the jira url back into this thread.
> it is not very helpful when you post huge fragments of code and markup
> into an email.
>
> -igor
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: Bug introduced somewhere after 1.2.2 is still in 1.3.3
Posted by Frank Silbermann <fr...@fedex.com>.
Here's the URL of my jira issue.
https://issues.apache.org/jira/browse/WICKET-1601
The issue has attached a quickstart project and a screen print.
-----Original Message-----
From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
Sent: Thursday, May 08, 2008 12:13 PM
To: users@wicket.apache.org
Subject: Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
On Thu, May 8, 2008 at 10:06 AM, Frank Silbermann
<fr...@fedex.com> wrote:
> I wrote earlier about my problems going from Wicket 1.2.2 to Wicket
> 1.2.6. This has to do with a RadioGroup component that I built;
> whenever I used it on more than one page, clicking on one RadioGroup
> caused the marker to disapper from all the other RadioGroups on the
> page.
>
> I wasn't given much help because Wicket 1.2 is end-of-life. Today I
> tried the example on Wicked 1.3.3. I downloaded the QuickStart
> application for Wicket 1.3.3, installed an upgraded version of my
> RadioGroup component, modified the home page to show my RadioGroup
> panel twice, and the bad behavior is still there.
>
> By the way, the only change in the generated HTML that I could see
> was that in Wicket 1.2.2 the buttons were defined:
>
> <input value="radios:2:radio" ...etc.
>
> -- with the numbers starting over again for each RadioGroup, whereas
> in Wicket 1.2.6 and Wicket 1.3.3 it was more like:
>
> <input value="radio7" ...etc.
>
> with the numbers _not_ starting over for each RadioGroup. Clicking
> on one radio group causes the marker to disappear from the other
> radio group -- as if part of Wicket were treating the buttons as
> though they all belonged to the same radio group.
>
> I'd like the Wicket 1.3 developers either to fix the bug in a future
> release (after which I'll upgrade my entire application to 1.3), or
> tell me what I'm doing wrong. How do I get the process started?
the usual way, create a jira issue and attach a quickstart project that
demonstrates the problem. than post the jira url back into this thread.
it is not very helpful when you post huge fragments of code and markup
into an email.
-igor
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Bug introduced somewhere after 1.2.2 is still in 1.3.3
Posted by Igor Vaynberg <ig...@gmail.com>.
On Thu, May 8, 2008 at 10:06 AM, Frank Silbermann
<fr...@fedex.com> wrote:
> I wrote earlier about my problems going from Wicket 1.2.2 to Wicket
> 1.2.6. This has to do with a RadioGroup component that I built;
> whenever I used it on more than one page, clicking on one RadioGroup
> caused the marker to disapper from all the other RadioGroups on the
> page.
>
> I wasn't given much help because Wicket 1.2 is end-of-life. Today I
> tried the example on Wicked 1.3.3. I downloaded the QuickStart
> application for Wicket 1.3.3, installed an upgraded version of my
> RadioGroup component, modified the home page to show my RadioGroup panel
> twice, and the bad behavior is still there.
>
> By the way, the only change in the generated HTML that I could see was
> that in Wicket 1.2.2 the buttons were defined:
>
> <input value="radios:2:radio" ...etc.
>
> -- with the numbers starting over again for each RadioGroup, whereas in
> Wicket 1.2.6 and Wicket 1.3.3 it was more like:
>
> <input value="radio7" ...etc.
>
> with the numbers _not_ starting over for each RadioGroup. Clicking on
> one radio group causes the marker to disappear from the other radio
> group -- as if part of Wicket were treating the buttons as though they
> all belonged to the same radio group.
>
> I'd like the Wicket 1.3 developers either to fix the bug in a future
> release (after which I'll upgrade my entire application to 1.3), or tell
> me what I'm doing wrong. How do I get the process started?
the usual way, create a jira issue and attach a quickstart project
that demonstrates the problem. than post the jira url back into this
thread. it is not very helpful when you post huge fragments of code
and markup into an email.
-igor
>
> /Frank
>
> -----Original Message-----
> From: Johan Compagner [mailto:jcompagner@gmail.com]
> Sent: Tuesday, April 29, 2008 12:31 PM
> To: users@wicket.apache.org
> Subject: Re: Change to API between Wicket 1.2 releases?
>
> I dont know what this is, but 1.2 is pretty much end of life, so you
> should try to debug what it is and patch your version Or just use a 1.2
> version that works for you
>
> On 4/29/08, Frank Silbermann <fr...@fedex.com> wrote:
> > I'm not sure what you mean by "what part it really is"? Are you
> > asking me to find a simpler example exhibiting the problem? I mean,
> > the panel class follows the RadioGroup component example quite
> closely:
> >
> > http://wicketstuff.org/wicket13/compref/;jsessionid=C6F7701B6426601795
> > 63
> > 84008732211C?wicket:bookmarkablePage=%3Aorg.apache.wicket.examples.com
> > pr
> > ef.RadioGroupPage
> >
> > The only significant difference is that instead of using a submit
> > button I override wantOnSelectionChangedNotification() to return true.
> >
> > public class MyPanel extends Panel {
> >
> > public MyPanel( String id,
> > String caption,
> > PropertyModel groupModel,
> > ChoiceOption[] options ) {
> >
> > super(id, groupModel);
> >
> > add( new Label("caption", caption) );
> >
> > final RadioGroup group = new RadioGroup("group", groupModel)
> {
> > // THIS IS THE ONLY PART THAT CHANGED FROM THE
> > COMPONENT EXAMPLE
> > protected boolean
> > wantOnSelectionChangedNotifications()
> > {
> > return true;
> > }
> > // IT POSTS BACK ON ANY SELECTION
> > };
> > add(group);
> >
> > List<ChoiceOption> optionList = Arrays.asList( options );
> >
> > ListView radios = new ListView("radios", optionList) {
> > protected void populateItem(ListItem listItem) {
> > listItem.add( new Radio("radio",
> > new PropertyModel(
> > listItem.getModel(),
> > "value")
> > )
> > );
> > listItem.add( new Label("option",
> > new PropertyModel(
> > listItem.getModel(), "label" )
> > )
> > );
> > }
> > };
> >
> > group.add(radios);
> > }
> >
> > Did I do something wrong, or is that feature of RadioGroup indeed
> > broken in current releases of Wicket 1.2?
> >
> > I really don't know enough about the Wicket internals to debug Wicket.
> > Can you suggest anything simpler that I could try to narrow down the
> > location of the problem? Would it work in Wicket 1.3?
> >
> >
> > -----Original Message-----
> > From: Johan Compagner [mailto:jcompagner@gmail.com]
> > Sent: Tuesday, April 29, 2008 3:54 AM
> > To: users@wicket.apache.org
> > Subject: Re: Change to API between Wicket 1.2 releases?
> >
> > 1.2 is a long time ago
> > I have no idea what change did break yours (and what did it fix) If
> > you could figure out what part it really is?
> >
> > johan
> >
> >
> > On Tue, Apr 29, 2008 at 12:09 AM, Frank Silbermann <
> > frank.silbermann@fedex.com> wrote:
> >
> > > I completed a Wicket 1.2 project a couple of years ago, and I've
> > > been maintaining it since then. I've been using Version 1.2.2
> > > successfully,
> >
> > > and figured I might as well use the lastest release of that version
> > > (1.2.7). Well, I'm trying to figure out why Wicket 1.2.7 broke my
> > code.
> > > (I scrounged up a Wicket 1.2.6 release, and that also breaks it.)
> > >
> > > Am I using the Wicket 1.2 API incorrectly? When it works in Wicket
> > > 1.2.2, am I using it in an unintended way? Let me illustrate what
> > > I've been doing with a small example.
> > >
> > > This is a simplified version of a component for creating and
> > > displaying radio button groups without having to write HTML every
> > > time. I give the
> > > constructor:
> > >
> > > (1) a wicket-id,
> > >
> > > (2) a PropertyModel that initializes the component and keeps track
> > > of the current choice, and
> > >
> > > (3) an array of ChoiceOption. -- The array of choice options
> > > defines the set of values offered by the radio buttons, and the
> > > corresponding labels to be displayed.
> > >
> > > The component posts back immediately when a change is made to the
> > > radio button. (Think fast INTRAnet with a very small number of
> > > simulaneous
> > > users.) Here is my implementation:
> > >
> > > package common.play;
> > >
> > > import wicket.markup.html.basic.Label; import wicket.model.IModel;
> > > import wicket.markup.html.panel.Panel; import
> > > wicket.markup.html.form.Radio; import
> > > wicket.markup.html.form.RadioGroup;
> > > import wicket.markup.html.list.ListItem; import
> > > wicket.markup.html.list.ListView; import wicket.model.PropertyModel;
>
> > > import java.util.List; import java.util.Arrays; import
> > > common.play.ChoiceOption;
> > >
> > > public class MyPanel extends Panel {
> > >
> > > public MyPanel( String id, String caption, PropertyModel
> > > groupModel, ChoiceOption[] options) {
> > > super(id, groupModel);
> > >
> > > add( new Label("caption", caption) );
> > > final RadioGroup group = new RadioGroup("group", groupModel) {
> > > protected boolean wantOnSelectionChangedNotifications() {
> > > return
> > true; }
> > > };
> > > add(group);
> > >
> > > List<ChoiceOption> optionList = Arrays.asList( options );
> > > ListView radios = new ListView("radios", optionList) {
> > > protected void populateItem(ListItem listItem) {
> > > listItem.add( new Radio("radio",
> > > new PropertyModel(
> > > listItem.getModel(),
> > > "value") ) );
> > > listItem.add( new Label("option", new PropertyModel(
> > > listItem.getModel(), "label" )));
> > > }
> > > };
> > >
> > > group.add(radios);
> > > }
> > >
> > > ----------------------------------------------------------------
> > >
> > > package common.play;
> > >
> > > public class ChoiceOption implements java.io.Serializable { public
> > > String value; public String label;
> > >
> > > public ChoiceOption(String value, String label) {
> > > this.value = value;
> > > this.label = label;
> > > }
> > > }
> > >
> > > --------------------------------------------------------------------
> > > --
> > > --
> > > ------------------------
> > >
> > > This is the layout for displaying my component. It's a divided box
> > > that puts the group caption in one half, and in the other half
> > > provides the set of labeled buttons. Note that I'm using a
> > > ListView, because each usage may require a different number of
> choices.
> > >
> > > <html xmlns="http://www.w3.org/1999/xhtml
> > > <http://www.w3.org/1999/xhtml> "
> > > xmlns:wicket="http://wicket.sourceforge.net/
> > > <http://wicket.sourceforge.net/> " xml:lang="en" lang="en"> <head>
> > > <link rel="stylesheet" type="text/css" href="style.css"/> </head>
> > > <body> <wicket:panel> <table border=1>
> > > <tr>
> > > <td>
> > > <span wicket:id="caption">Caption</span>
> > > </td>
> > > <td>
> > > <span wicket:id="group">
> > > <table cellpadding=5>
> > > <tr>
> > > <td wicket:id="radios" align="center">
> > > <input type="radio" wicket:id="radio"/>
> > > <span wicket:id="option">option name</span>
> > >
> > > </td>
> > > </tr>
> > > </table>
> > > </span>
> > > </td>
> > > </tr>
> > > </table>
> > > </wicket:panel>
> > > </body>
> > > </html>
> > >
> > >
> > > Here is a page with two intances of this component; one set of radio
>
> > > buttons below the other, within a form. Below my form are two
> > > labels, one below the other, which indicate the value currently
> > > chosen by the corresponding radio-button set.
> > >
> > > import wicket.markup.html.WebPage;
> > > import wicket.markup.html.panel.Panel; import
> > > wicket.markup.html.form.Form; import wicket.model.PropertyModel;
> > > import wicket.markup.html.basic.Label; import
> > > common.play.ChoiceOption;
> > >
> > > public class MyPage extends WebPage {
> > >
> > > public String firstProperty = "A";
> > > public String secondProperty = "A";
> > >
> > > ChoiceOption[] options = { new ChoiceOption("A", "Ay"),
> > > new ChoiceOption("B", "Bee"),
> > > new ChoiceOption("C", "See"),
> > > new ChoiceOption("D", "Dee") };
> > >
> > > public MyPage() {
> > >
> > > Form form = new Form("form");
> > > add( form );
> > >
> > > Panel panel1 = new MyPanel( "panel1",
> > > "1st choice",
> > > new PropertyModel( this,
> > > "firstProperty"),
> > > options
> > > );
> > > form.add( panel1 );
> > >
> > >
> > > Panel panel2 = new MyPanel( "panel2",
> > > "2nd choice",
> > > new PropertyModel( this,
> > > "secondProperty"),
> > > options
> > > );
> > > form.add( panel2 );
> > >
> > > add( new Label( "result1",
> > > new PropertyModel(this, "firstProperty")
> > > )
> > > );
> > >
> > > add( new Label( "result2",
> > > new PropertyModel( this, "secondProperty")
> > > )
> > > );
> > > }
> > > }
> > >
> > >
> > > <html xmlns="http://www.w3.org/1999/xhtml
> > <http://www.w3.org/1999/xhtml>
> > > " xmlns:wicket="http://wicket.sourceforge.net/
> > > <http://wicket.sourceforge.net/> " xml:lang="en" lang="en"> <head>
> > > <link rel="stylesheet" type="text/css" href="style.css"/> </head>
> > > <body> <form wicket:id="form" id="form" name="form"> <span
> > > wicket:id="panel1"> first radiobutton set appears here </span>
> > > <span wicket:id="panel2"> second radiobutton set appears here
> > > </span> </form> <div wicket:id="result1"> first selected choice
> > > appears here</div> <div wicket:id="result2">second selected choice
> > > appears here</div> </body> </html>
> > >
> > > This works just fine in Wicket 1.2.2, but when I use Wicket 1.2.6
> > > or Wicket 1.2.7, I find that when I move the black dot by selecting
> > another
> > > choice in one group, the black dot in the other group disappears.
> > > Sometimes both dots disappear.I play with the radio buttons the
> > > black dot disappears, even though the model for each button group
> > > maintains the proper value.
> > >
> > > The disappearance of the indicator dot is merely the most obvious
> > > manifestation of the problem. By application is crashing like crazy
>
> > > with Wicket 1.2.7, but works just fine with Wicket 1.2.2.
> > >
> > > Am I using the Wicket 1.2 API incorrectly? Is there some problem
> > > with my use of ListView, or PropertyModel? When it works in Wicket
> > > 1.2.2,
> > am
> > > I taking advantage of undocumented behavior? What am I
> > > misunderstanding? If this is the result of a change that was made
> > > for improved AJAX support, what would be my simplest work-around?
> > >
> > > /Frank
> > >
> > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org