Thank you! I was getting confused. Actually, I took a peek at the article,
saw that it was about the same sort of optimistic locking mechanism that
I've been building for years and skipped it.
FYI, Persistence had some support for this sort of thing in their OR
mapping toolset (in C++ anyway) a few years ago.
On Sat, 28 Oct 2000, Rickard �berg wrote:
> Hey
>
> Dan Christopherson wrote:
> >
> > I'm rather used to building this sort of optimistic lock feature in
> > application land. I'm not sure how this would look in an EJB container.
> >
> > What would the client (i.e. servlet/jsp)'s view of this long transaction
> > be? would I create a UserTransaction and keep it hanging around in my
> > session? I don't think i'd like that - I like to be able to differentiate
> > between the long 'transaction' and the actual DB transactions. Or maybe
> > that's just me.
>
> No.. Marc misunderstood the article. This is something *you* do as bean
> developer, and you catch this when doing setData() on your bean after
> the client has edited the values. If there's an exception then it has
> been changed since the client did getData() to get values to work with.
>
> /Rickard
>
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
Dan Christopherson (danch)
nVisia Technical Architect (www.nvisia.com)
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
