Server side state as a performance problem is WAY overrated. If you're not
working for Google, it's probably not a problem.
That said: if your Web application has state it has state however much you
may wish it were not so. The only way to remove that state is when you move
it to the client. Then,
Hi,
I have been looking at how to set the value of a radio input field to
a value of my choosing.
If I use the Radio and Radio Group code as shown here:
http://pastebin.com/m40b9b073
I get html such as
input wicket:id=radio type=radio value=radio2
name=selectionGroup/
input
The approach with
Component radio= new Radio(radio, ...);
is the right one. You can still try to add the AttributeModifier, but
probably, you'll end up fighting the Radio implementation (perhaps you'll
have to create a subclass?)
However, I don't see why you don't just use the regular wicket
Thanks for the tip Thomas! I have it now.
I am really keen to avoid state on the servers, as a design principle.
It forces me to think the web way as much as possible, and when one
does, possibilities start becoming evident. So no I did not do any
measurements there. But these principles
