As dbms choice and database setup (dialect, connection, pool
configuration) are highly individual and need to be done manually either
way, I don't see the need to include a dependency on tapestry-hibernate
in the quickstart just so that a potential user doesn't have to add it
to his POM by himself.
It would be different though, if we shipped the quickstart with a
dependency on HSQLDB (and a working hibernate.cfg.xml for it) and some
example entities.
Uli
Howard Lewis Ship schrieb:
The title says it all. It would be very easy to include
tapestry-hibernate as a dependency, and a minimal hibernate.cfg.xml
file as well. Thoughts?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
