Unfortunately, I prefer use JDBC to Hibernate. I'm not using Hibernate in my projects.
If I'm stick to JDBC, is it better to stick with Spring Service for declarative transaction and accessing database ? Thanks in advance On Sat, Dec 11, 2010 at 11:53 PM, Josh Canfield <joshcanfi...@gmail.com> wrote: > For most cases using tapestry-hibernate should be sufficient. Have you > looked at that? > > http://tapestry.apache.org/current/tapestry-hibernate/userguide.html > > Are you doing something that would make this not sufficient? > > On Sat, Dec 11, 2010 at 2:36 AM, Yohan Yudanara > <yohan.yudan...@gmail.com> wrote: >> Hi.. >> >> Tapestry 5.2 live service reload is awesome. >> However, I'm used to accessing database using Spring JdbcTemplate >> (using spring bean with @Repository annotation) and manage transaction >> using spring declarative transaction (in ApplicationContext.xml). >> >> I'm considering to use tapestry service instead of writing service as >> spring bean (because of live service reload feature). >> When I'm using tapestry service, what is the best practice for >> accessing database using JDBC and managing transaction? >> >> Could someone give me a clue? >> >> Thanks in advance. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
