Hi, after much evaluation I have finally decided to go with Wicket as the main framework for a new enterprise site and I think I'll be pleased. I have a long road ahead of me though, because while I have much experience with developing desktop applications I'm afraid my understanding of the http request cycle will initially make it hard to just "let go" and stop micromanaging...
But anyway, what I still haven't decided is which ORM (if any) framework that I should go with. I have previously developed an in-house ORM system which has all the basic features I need (lazy-loading, easy population of beans, an object-oriented query language etc.), but I'm well aware of that I did it to begin with because I was afraid of letting go of my precious sql statements. Not having perfect control of the generated sql statements would be hard, but I guess I just have to wake up and realize that perhaps in these days it doesn't really matter if an sql statement or two could be optimized if you were to perform the joins in this way instead or whatnot. I was hoping I could get some feedback on how people have worked with different ORMs with Wicket. I have some experience with Hibernate, though it was a little to much of a blackbox to me when I used it. For example, I see that DataBinder has popped up as a bridge between specifically Wicket and Hibernate. Any comments on how well it works? Thanks in advance, Matthias ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
