Which is true, but if you aren't going to use the facilites of Tapestry, such as its built-in Hibernate integration, then please seek answers to your problems elsewhere.
Using the Tapestry mechanisms means that the you can be sure of using the same session instance across all pages, components and services (within a transaction). The session will be created only as needed and will be discarded automatically at the end of the request. You can use @CommitAfter on any component method, and can configure you services to recognize it as well. In addtion, you have added in-Tapestry hooks to configure Hibernate at startup, and Tapestry will automatically register entity beans it finds in your applications' entities package, and automatically set up URL encoding/decoding of entity objects. It's actually quite a lot. So there's reasons to use the right tools. But again, if you want to use some other approach, that's fine ... just don't seek help here. Go on the Hibernate mailing lists. On Fri, Oct 8, 2010 at 12:07 AM, ael <alan-lua...@dash.com.ph> wrote: > > So what would be the difference? > The important is you achieve > what you want to do. > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Early-steps-getting-Tapestry-and-Hibernate-working-via-DAO-tp3072498p3204134.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
