It really depends on your preferences. Either a databinder (using JPA related classes directly in your UI code) or a DAO/ services based approach will work.
Eelco On Tue, May 13, 2008 at 8:29 AM, David Nedrow <[EMAIL PROTECTED]> wrote: > I have a data "driver" package built around JPA and an Entity Manager > Factory (javax.persistence.EntityManagerFactory). This is currently used by > a couple of standalone applications and works well. > > What is the best way to leverage this package in the context of a > Wicket-based web application? IE., how best to instantiate the factory (if > necessary) and/or use the DAOs. Should this happen at the wicket application > level, or somehow page/panel-based? > > Thanks for any pointers, > > -David > > --------------------------------------------------------------------- > 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]
