This is something that is really needed, but I have some questions. Why do you not use Hivetranse for session/transaction management? There has already been done alot of work on that. It is a clean Hivemind contribution. Check it out! http://hivetranse.sourceforge.net/
Also, as you are using Java 5.0, I think you should consider using the following patterns for generic data access objects: http://www.hibernate.org/328.html Another thing is the HibernateSqueezer on the wiki. I think it is really a good thing, and easy to implement thanks to Hivemind. http://wiki.apache.org/jakarta-tapestry/HibernateTapestrySqueezer?highlight=%28hibernate%29 /ted On 1/16/06, Schulte Marcus <[EMAIL PROTECTED]> wrote: > I've put together a new release of KickStart, a Tapestry/Hivemind/Hibernate > application template implementing the hibernate-session-per-conversation > pattern (http://kickstart.sourceforge.net). > > Biggest Improvement: Conversations now have their own lifecycle. They can be > terminated without affecting the http-session. To achieve that, I've added a > new PropertyPersistenceStrategy "conversation". It stores properties in a > new, session-scoped ASO, which also holds the hibernate session. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
