entity bean as being reentrant
in [Java Programming]
|
From: gk on 19 May 2010 09:05 Here is a excerpt If we define the entity bean as being reentrant, multiple clients can connect to the Entity bean & execute methods within the entity bean concurrently. Container takes care of synchronization. If we define the entity bean as non-reentrant and many clients connect to it concurrently to execute a method, exception is thrown . could you please tell what exception ? is it java.lang.Exception ? or something else ? Also , why there is no re-entrant for session beans ? is there any reason ?
From: Lew on 19 May 2010 12:59 gk wrote: > Here is a[n] excerpt excerpted from ...? > If we define the entity bean as being reentrant, multiple clients can > connect to the Entity bean& execute methods within the entity bean > concurrently. Container takes care of synchronization. If we define > the entity bean as non-reentrant and many clients connect to it > concurrently to execute a method, exception is thrown . > > could you please tell what exception ? What do the > is it java.lang.Exception ? or something else ? *All* exceptions in Java are 'java.lang.Exception's. They may be something else as well. What does the documentation say for your platform? > Also , why there is no re-entrant for session beans ? is there any > reason ? Stateless session beans are re-entrant, or can be. Stateful ones really cannot be. Things are somewhat different in modern Java EE. For what platform is that documentation? What document did you excerpt? -- Lew
|
Pages: 1 Prev: change ISO8859-1 to GB2312 Next: php and java type mapping via SOAP |