Roberto,
come on man, not you!
do me a favor, pull those fingers out of your *rse and go look at the
locking strategy for the stateful container (StatefulTxInterceptor)
something like that.
What is going on? a former "paratrooper" is growing into a fat cat at
Siemens? and expect a legion of minions to explain code he used to recite
like the bible a couple of month ago?
You know I can't tolerate that...
Come on... go wash those fingers...
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Roberto
|Leong
|Sent: Wednesday, April 04, 2001 6:38 PM
|To: '[EMAIL PROTECTED]'
|Subject: [JBoss-user] transaction strategy of jboss
|
|
|Hi
|
|I´d like to know how the locking mechanism works for stateful session beans
|in jboss, to be more precise imagine I have session bean like this:
|
|TestSB {
| EntityBean bean;
|
| create(EntityBean bean){
| this.bean = bean;
| }
|
| doSomeStuff(){
|
|
| bean.someStuff()
| }
|}
|
|is the bean locked from the create of TestSB until it´s destroyed? locked
|during the execution of beans´s methods? locked during the execution of the
|TestSB methods? or is it dependent on the transactions properties
|of TestSB?
|
|if someone could explain how the locking mechanism works or just give me
|some pointers to resources I´d appreciate
|
|regards
|Roberto
|
|_______________________________________________
|JBoss-user mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
