Hi,
I'm currently doing some research in order to find a better tool than plain JSP to do user interfaces in our projects. I first thought that tapestry would be something we would use, but after that I (almost accidentally) bumped into Wicket, which seems more cleaner and simpler solution to same problem (which makes it easier to learn, at least to me).
Our typical application contains usually many forms. Each form can contain many (say 10...30) fields. Data comes from database with our own OR-mapper, which provides POJO-like models.
After prototyping with wicket I have some questions:
- On a large form, which has many fields it would be nice to be able to auto-wire fields to model properties automatically. (ie. I have a text field called "userName" in html form and I have property called "userName" in my model). This would speed up development a lot. I don't know if this would work for everyone, but we have most of business-level validation logic in models so simple validation in wicket layer (like just checking that field is a number) is enough.
I'm going to implement something like this if it doesn't exist already.
- Empty TextFields seem to be stored into model as Strings with zero lengths. Our previous UI system maps empty strings to nulls. Is there a way to tweak this anywhere in wicket ?
- Is it OK to create instances of page objects myself, ie. doing something like this: getPage().setResponsePage(new PersonListPage(coll)); or should pages be instantiated by some factory class ?
Ari S.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
