I'd like to start a thread on Dominik Drzewiecki's suggestion of a type-safe property model improvement for Wicket 7. I've seen a few competing solutions:
1. Igor's metagen: https://github.com/42Lines/metagen 2. Igor's bindgen-wicket: http://code.google.com/p/bindgen-wicket/ 3. Carl-Eric's wicket-safemodel: https://github.com/duesenklipper/wicket-safemodel We use our own metagen-like solution (written before Igor's) for use in PropertyModels and JPA/Hibernate criteria queries, but we've been eyeing... 4. Querydsl (http://www.querydsl.com/) ... as a JPA/Hibernate query alternative. To avoid redundant Maven plugins and generated classes, I've been meaning to explore adapting Querydsl's Q* classes into a Wicket IModel. This approach is too heavy for a Wicket "core" feature, but I mention it because on the surface it seems like the cleanest option for JPA-backed Wicket projects. Is there a clear "best" here (or elsewhere)? Worst? :) Igor, is it accurate to say that metagen supercedes bindgen-wicket? Is it a reasonable goal for this to be a core feature, or does its probable Maven plugin relegate it to another (experimental?) module? Cheers, Dan
