Once again, I recommend that you have a look at JDO. Just like JPA, it is a standardized specification with several providers.
Differently from JPA, it also allows one to use OODBMSs, Excel, Google BigTable, Amazon EC2 and so on in addition to relational databases. By selecting JPA you cut of the possibility to use e.g., db4o as persistence engine. (IMO there are far too many systems out there that routinely use a RDBMS as persistence engine. In many cases an OODBMS would have done the job with significantly less development effort.) Olle Hallin Senior Java Developer and Architect olle.hal...@crisp.se www.crisp.se http://www.linkedin.com/in/ollehallin 2010/1/12 Piero Sartini <li...@pierosartini.de> > > As far as I understand, javax.persistence.EntityManager is an interface, > so, > > there should be any mechanism to determine which impl will be used at > > runtime, right? > > Right. This is part of the JPA specification. You define the > implementation inside your persistence.xml: > ... > <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> > ... > > Piero > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
