Where does your "fields" come from ? In WWB, you have to provide beans,
and configure them with annotations or beanprops files to control the way
the beans are displayed.
You can provide beans and they will be correctly displayed in a default
way, with proper editing inputs according to the datatype of each field. But
both the beans and the (optional) configurations need to be coded, you will
not be able to provide WWB with a stream of "isolated" fields.
Regarding validations, some are provided by WWB itself (required),
anything else will be rather hard to add with standard WWB, but you can
provide customized input field implementations (see customfields example).
Of course those custom fields will not be used by default, you will have to
configure the properties to use them.
See live examples here:
http://jweekend.com/wicketwebbeans-examples-1.1/WebBeans/
And the source code for the examples here:
http://code.google.com/p/wicket-web-beans/source/browse/#svn/trunk/wicketwebbeans-examples/src/main/java/com/googlecode/wicketwebbeans/examples
Hth,
Daniel
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Re-Wicket-Web-Beans-tp2326481p2327195.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
