Thank you invisiblemage,
I'll try to adapt your example to my problem.
Moreno
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844219#3844219
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844219
-
>>But in this case I must lock the "user/pk" table instead of
>>"my data" table: where is the difference ?
You do the following:
(Server Code)
try {
locktable.findByUserLock(user,row_to_lock);
return false;
} catch (FinderException e) {
insert(user,row_to_lock); // can only be inserted of
invisiblemage wrote:
>So, are we talking of "real" clients, that read some data, display it to the user,
>and after 20 minutes the user commits new data?
Yes.
>Then it is really no good practice to keep the entity-reference on the client (with a
>transaction open ?!!) - the client should neve
So, are we talking of "real" clients, that read some data, display it to the user, and
after 20 minutes the user commits new data?
Then it is really no good practice to keep the entity-reference on the client (with a
transaction open ?!!) - the client should never ever have direct access to an e
I need this behaviour because I wanna avoid this situation:
CLIENT 1 starts modifying some data:
it reads data, updates them (using a GUI) and writes them in the DB.
if CLIENT 2 starts after CLIENT 1's start, but before CLIENT 1's update,
it can try to write in DB "no more valid" data
I prefer t
just wondering why you would like that behaviour ???
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844073#3844073
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844073
