i have written a lot of listviews and repeaters and never had to
override onrender to render html, this is now how wicket is intended
to work. in wicket you attach components to html elements, and the
only contract is that certain components expect to be attached to
certain elements. for example a
Thanks for the response. I have two thoughts.
1) So you would say that expected Wicket best practice would be what?
My control is effectively a TextField. Would I extend
AbstractTextComponent (which I see has almost every property TextField
has) and then add() a TextField and a Label to it, and
in wicket you would not override the textfield and make it render as a
label, thats what the label component does. you would create a
component that would either add a textfield or a label based on some
condition.
-igor
On Thu, Apr 22, 2010 at 9:42 AM, Brian Mulholland
wrote:
> I have figured ou
I have figured out issue #2. My form had a method='get' on it and I
have a very large grid with checkboxes in it, so I suspect that I was
overflowing the request size. Stupid mistake, but the behavior in no
way pointed me towards this. On the observation I made that it seemed
to work when I remo
I am a Wicket n00b. Just learning and writing a demo app to evaluate
Wicket vs a few other MVC solutions which are having demos written by
other developers in the group. I am having two issues.
Issue 1 involves me trying to write a custom TextField to demo the
idea of overriding a control and ou
