> Sent: Tuesday, January 17, 2006 4:49 PM
> To: Tapestry users
> Subject: RE: Kickstart 0.2 released
>
>
> Session per request is the simplest
> and most efficient approach in many cases and it does not
> require Java 5. Please look at the barebone
e it a cooler name
> and add all kinds of good stuff from Jesse's toolbox (integration for
> remoting, jms, drools, and more).
>
> > -Original Message-
> > From: Konstantin Ignatyev [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, January 17, 2006 4:49 PM
>
PROTECTED]
> Sent: Tuesday, January 17, 2006 4:49 PM
> To: Tapestry users
> Subject: RE: Kickstart 0.2 released
>
>
> Session per request is the simplest
> and most efficient approach in many cases and it does not
> require Java 5. Please look
Session per request is the simplest and most efficient
approach in many cases and it does not require Java 5. Please look at the
barebone implementation with CGLib alone:
http://sandbox.sourcelabs.com/kosta/hibernate-bhw/java/com/sourcelabs/hibernate/bhw/haop/doc/haop.ht
Yeah, definitely. Marcus's code is very good. It feels like we've found a
keeper. I think we can all agree that having an integration point similar to
SEAM would be a huge help in dropping the barrier to using tapestry.
On 1/17/06, Chris Chiappone <[EMAIL PROTECTED]> wrote:
>
> Jesse is the tacos
Jesse is the tacos guy, and I think he meant kickstart vs hivetrans
when he was talking about competition.
On 1/17/06, Ted Steen <[EMAIL PROTECTED]> wrote:
> oups!
> just read about the property-persistence-strategy "conversation"
> so the cache size would not be a problem.
> nice..
>
> On 1/17/06
oups!
just read about the property-persistence-strategy "conversation"
so the cache size would not be a problem.
nice..
On 1/17/06, Ted Steen <[EMAIL PROTECTED]> wrote:
> hi!
>
> I think the generic data access objects on the hibernate page could be
> usefull as they, among other things, support a
hi!
I think the generic data access objects on the hibernate page could be
usefull as they, among other things, support a generic way to specify
the id (not only long).
One thing that I come to think about regarding the
session-per-conversation pattern is that there could be memory issues.
the se
hi ted,
thanks for the feedback!
> 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/
>
That's a story which went a bit "unlucky". Last summ
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
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
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
12 matches
Mail list logo
