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]

Reply via email to