i don't really (have the time right now to) fully understand this thread,
but at the risk of saying something obvious, i wanted to point out that
although wicket components in a listview don't have unique names, they do
have unique /paths/ because their parent container is named with the row
number.


Ittay Dror wrote:
> 
> 
> 
> Ittay Dror wrote:
>> 
>> 
>> b. have all repeating elements have the same name. the problem is that
>> components won't be updated correctly if some fields do not appear, or
>> i'll need to modify getInputAsArray for each (so as to look in the query
>> string,  not the parsed parameters), and give each an index.
>> 
>> i'm looking for a better way.
>> 
>> 
> 
> i think this can be solved inside wicket quite easily:
> * FormComponent.getInputAsArray uses
> 'getRequest().getParameters(getInputName())'.  instead, it would be
> 'getParent().getRequestParameters(this, getInputName())', 
> * the default implementation of getRequestParameters(Component, String) in
> Component will be getRequest().getParameters(getInputName())
> * In the above case, when creating a ListView, use a subclass that
> modifies getRequestParameters() so it returns the parameters from the nth
> occurrence of the parameters (the nth 'atext=xx&acb=yy' segment)
> 
> then, form components can be used as they are.
> 
> ittay 
> 

-- 
View this message in context: 
http://www.nabble.com/dynamically-%28client%29-created-form-components-tf3325801.html#a9333058
Sent from the Wicket - User mailing list archive at Nabble.com.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to