It depends. If you want to use transaction-per-request with open-session-in-view, then it could work for you now. If you need conversation support (something we're working to build in), then it's not ready for you just yet. Tapernate can automagically reattach your persistent page properties (that are Hibernate entities) to the current session quite easily. And, the POJO rollback feature will save you some headaches if you use the TransactionUtils.setRollbackOnly method, which will be moving to another module (the one that defines all the transaction stuff in the first place, spring.transaction), since it's really not related to tapestry at all.
-----Original Message----- From: Hugo Palma [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 24, 2006 9:48 AM To: Tapestry users Subject: Is Tapernate production ready ? I know it's a WIP, still, how confident can i be when choosing to use Tapernate in a project starting in a few weeks ? Is there any estimate to when the project will be rock solid, with the production ready stamp ? I mainly looking for Jame's opinion and from everyone that has used Tapernate in a medium/big size project. Thanks in advance, Hugo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
