You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Schulte Marcus <ma...@bmw.ch> on 2006/01/16 08:20:10 UTC
Kickstart 0.2 released
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: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Kickstart 0.2 released
Posted by Jesse Kuhnert <jk...@gmail.com>.
I have finally sat down and done some initial examinations of the kickstart
code, and I like it a lot :) I hope the project continues to flower and grow
as I like the design principles and overall goals he's moving forward with
very much.
A little competition is always a healthy thing for soft dev right? ;)
On 1/16/06, Ted Steen <te...@gmail.com> wrote:
>
> 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 <ma...@bmw.ch> 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: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
Re: Kickstart 0.2 released
Posted by Ted Steen <te...@gmail.com>.
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 <ma...@bmw.ch> 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: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org