)
{
this.stateManager = stateManager;
}
}
-Original Message-
From: Anthony Fox [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 23, 2006 8:57 AM
To: Tapestry users
Subject: Re: hibernate detached objects as persistent page properties
Thanks for the code. I'll take a look an
is stuff works for you guys! Let me know if I can help with
> anything.
>
>
> -Original Message-
> From: Andreas Bulling [mailto:[EMAIL PROTECTED] On Behalf Of
> Andreas Bulling
> Sent: Wednesday, February 22, 2006 1:33 PM
> To: Tapestry users
> Subject: Re: hibe
February 22, 2006 1:33 PM
To: Tapestry users
Subject: Re: hibernate detached objects as persistent page properties
On 22. Feb 2006 - 13:30:00, James Carman wrote:
| Okay, folks. I've abstracted out the Hibernate/Tapestry stuff into its
own
| project called "Tapernate." You can downloa
On 22. Feb 2006 - 13:30:00, James Carman wrote:
| Okay, folks. I've abstracted out the Hibernate/Tapestry stuff into its own
| project called "Tapernate." You can download the source and build it
| yourself (the libs are there for you) from SVN:
|
| http://www.carmanconsulting.com/svn/public/tap
ourse, if you guys find something wrong with it, I'll fix it because I'm
using it in my own project. Enjoy!
-Original Message-
From: Anthony Fox [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 22, 2006 12:43 PM
To: Tapestry users
Subject: Re: hibernate detached objects as per
I don't want to expose the hibernate session to tapestry pages and
components. I would rather keep the ui layer unaware of detached
objects or the mechanism of reattaching those objects or even whether
an object is detached or not. I'm looking for a way in which I can
reattach the objects transpa
On 22. Feb 2006 - 12:51:19, James Carman wrote:
| Hold your horses. I've almost got my stuff set up in SVN for you all to
| check out. I'm creating a project called "Tapernate" (cheesey, I know).
I nearly can't wait any longer and I'm counting the minutes :-)
Wooo, when I posted my question one
You could do reattach objects with hibernateSession.lock( object,
LockMode.NONE), but I suggest explicit reattaching with session.merge( object ).
Explicit merging is better IMO because easily allows "wizard"-like multi
iteration editing of an object and then persisting all the changes if desired
ry users
Subject: Re: hibernate detached objects as persistent page properties
I have considered a similar solution as I use Spring as well.
However, I was looking for a way to not have to _explicitly_ reattach
objects. Rather, I would like all persistent detached objects in the
session&#
I have considered a similar solution as I use Spring as well.
However, I was looking for a way to not have to _explicitly_ reattach
objects. Rather, I would like all persistent detached objects in the
session's context to reattach automatically. A filter or interceptor
with knowledge of what obj
I'm doing this in several applications. I normally use Spring also, but
that is not really necessary. Tapestry isn't aware of the persistence
implementation, but it does have to explicitly attach (and occasionally
merge or evict) detached objects. Since I reference my DAO services in
my Tapestry
Sure, I would like to take a look. Could you email it to me or make
it available?
On 2/22/06, James Carman <[EMAIL PROTECTED]> wrote:
> Well, I wrote something pretty cool the other day. It's a new storage
> strategy for Tapestry called "entity." Basically, if you try to store an
> object as a
Well, I wrote something pretty cool the other day. It's a new storage
strategy for Tapestry called "entity." Basically, if you try to store an
object as a persistent page property that is a persistent entity, it doesn't
store the actual object. It stores its identity information
(entityName/id).
13 matches
Mail list logo
