anonymous wrote : Regarding older EJBs using 1.0 deployment descriptors but deployed
into 3.2.3 container, can the container manage optimistic locking for these?
|
No.
anonymous wrote : Regarding last post, this seems to contradict what is printed in the
Admin/dev guide.
What is
Regarding older EJBs using 1.0 deployment descriptors but deployed into 3.2.3
container, can the container manage optimistic locking for these?
Does documentation exist re: the config for Optimistic using the 1.0 EJBs?
Regarding last post, this seems to contradict what is printed in the
1) yes
2) no
3) yes, it's a cmp field
5) what does weblogic do here that jboss does not?
To objec's post. This behaviour is expected. Optimistic locking is used to prevent
concurrent updates to the data with the same version. When second client invokes a
getter, the instance is reloaded from
anonymous wrote : I have this questions for Juha:
| 1)When bean developer specifies version control attribute, does jboss update its
value?
| 2) If it does, then does jboss compare its value in Value Object Pattern scenario
and throw any exception? If it does then what is the exception type?
