On 5/24/06, James Carman [EMAIL PROTECTED] wrote:
No problem! Just to be clear about why your situation is working now, I
removed the transaction interceptor from the persistence strategies and the
squeezer. With transaction-per-request turned on, these features work
just fine. You can
, 2006 9:36 AM
To: Tapestry users
Subject: Re: New version of Tapernate...
On 5/24/06, James Carman [EMAIL PROTECTED] wrote:
No problem! Just to be clear about why your situation is working now, I
removed the transaction interceptor from the persistence strategies and
the
squeezer
Message-
From: Henri Dupre [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 24, 2006 12:18 PM
To: Tapestry users
Subject: Re: New version of Tapernate...
Hi James,
On 5/24/06, James Carman [EMAIL PROTECTED] wrote:
2. Taperate now has support for three types of property persistence,
reattach
One question,
If I retrieve an object from my DAO and change something in that
object without doing a session.update(...), the change will be
persisted (to the DB). Is this the way it should work (not having to
do a manual update) ?
public Product getProduct()
{
Product product;
PROTECTED]
Sent: Wednesday, May 24, 2006 1:28 PM
To: Tapestry users
Subject: Re: New version of Tapernate...
One question,
If I retrieve an object from my DAO and change something in that
object without doing a session.update(...), the change will be
persisted (to the DB). Is this the way it should
this very topic:
http://www.theserverside.com/news/thread.tss?thread_id=40581
-Original Message-
From: Marcus Matèrn [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 24, 2006 1:28 PM
To: Tapestry users
Subject: Re: New version of Tapernate...
One question,
If I retrieve an object from my DAO
