we don't set the values. We only do that when there is nothing returned in the get
If a collection is returned by the get that collection is filled with the values.
But as far as i know we always did that, there is some code changed i think but we couldn't just
set a List in it. Because who is telling us that it is a list and not a set?

johan


On 4/20/06, Dave < [EMAIL PROTECTED]> wrote:
I just upgraded wicket in my project from snapshot 20060302 to Release
Candidate 2 and am currently testing it.

I find that a ListMultipleChoice, which is accepting multiple
selections, is no longer receiving the selections made by the user. The
ListMultipleChoice is created with a PropertyModel that has a setter
with a List as parameter, but it is never called when I submit the form.
The getter is called just fine prior to showing the form to the user.

Is this a bug introduced somewhere between snapshot 20060302 and Release
Candidate 2 or do I have to change something as result of changed API?

Thanks in advance and best regards,

Dave








-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to