Josh, I agree with you about the need to try to understand Wicket a bit first before diving into ORM-izing (I coined it first; I call dibs) your application.
However, for those who want to start with a hibernate-based or jpa-based application, it's nice to have a good starting point (like a maven archetype). With "wicketopia", we've got two different archetypes for JPA and Hibernate. Wicketopia itself is based on the Domdrides core API, so it is ORM implementation agnostic. James On Tue, Sep 23, 2008 at 4:10 PM, jchappelle <[EMAIL PROTECTED]> wrote: > > I think it is important to understand that Hibernate and Wicket are two > completely different frameworks that are built to solve different problems. > Hibernate operates at the data access layer and wicket at the gui > layer(mostly). You don't need hibernate to get your data to wicket. > > I don't know about any of those other frameworks but I think it is a good > thing to have a distinction between these two layers. That way you can > choose a framework for each layer that will be well suited for the problem > you are trying to solve. > > So when going through the wicket examples don't even worry about hibernate. > Just dummy up a list of strings or some other pojos and display them on the > screen just to get it going. Then once you have that, you can choose to get > the real data from wherever you please, however you please. > > Thanks, > > Josh > -- > View this message in context: > http://www.nabble.com/Wicket-sample-application-tp19549890p19635913.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
