You should pick the last 1.4 stable version, as of the time of this email, would be 1.4.17.
Secondly, Hibernate is an implementation of JPA and has no relationship with Wicket, but it has with Spring. You may drop all of your Spring MVC code, and keep the rest of its service and data layers. Why don't you run your system and save the screens in static HTML files? That way it will be easier to apply the wicket:id modifiers to dynamic nodes. Then you will only have to code the presentation layer of Wicket as Java classes. Also, get Spring 3.0.5. *Bruno Borges* www.brunoborges.com.br +55 21 76727099 On Mon, Jul 25, 2011 at 2:37 PM, eugenebalt <eugeneb...@yahoo.com> wrote: > Thanks, so I should choose > > Wicket 1.4.12, Spring 3.0.2, JPA 2.0 ? > > I didn't see a Hibernate option in that list. Hibernate is an > implementation > of JPA? > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Replacing-Spring-MVC-with-Wicket-in-Existing-Spring-Hibernate-project-tp3693395p3693440.html > Sent from the Users forum 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 > >
