Hi!
"Bordet, Simone" wrote:
> > But in this case all calls are
> > made without transactions.
>
> Noo, why ? They will run with their transactions, like a normal call.
> Oh wait, you mean that you explicitely set TRANSACTION_NEVER in the
> deployment descriptor ? If so, not good IMHO.
I think he's using TX_SUPPORTS, which is recommended in these cases.
> > What does pessimistic concurrenct mean in
> > that situation?
> >
> > Say that cash register 1 and 2 at the same time scans a jBoss box,
> > instanciates a MySession which will call the findByPrimaryKey for the
> > jBoss item to get price/description. Will there be 1 or 2 instances of
> > the jBoss item?
>
> One.
Exactly, although note that this is an implementation detail of the
default cache. There is nothing that prevents us from adding an
alternative implementation that utilizes multiple instances
concurrently.
In fact, if any of you have a great desire for one, and have a basic
understanding for how to construct one, please do.
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
