> So, do you think that the most flexible approach should be to have some
> module like tapestry-jpa to interact with into the pages, and, the real
> "data access layer" implementation could be inter-changable between
> hibernate, db4o, and anyone which implements the JPA specification?
If you use JPA, you may switch between the implementations:
EclipseLink / Toplink, Hibernate, OpenJPA and DataNucleus to name a
few.
In practice I have never seen a project changing its underlying
database.. but well, you may do this with JPA as well.
For db4o, as it is no relational database I don't think it provides a
JPA implementation. And if it does, I would not use it - you loose the
power of object oriented databases by doing so. I've used NeoDatis
(another OODB) myself and wrote a small plugin equal to tapestry-jpa
to make its usage more pleasant (injecting ODB service and working
@CommitAfter). You could take the same approach for db4o.
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
