Hi!
I've looked through the archives but couldn't find an answer to this
specific question. Previous discussions I found only discussed server to
client callbacks at a later point in time (asynchronous calls, which JMS
will provide), or calls like afterCommit() and such (not actual callbacks
in my opinion). What I am looking for is an answer to whether or not it is
possible to provide concurrent (actual) callbacks, that execute in
parallell with the bean requesting the callback.
For example, I have beans A and B. A uses B to call itself for some
configuration. The calls made are:
1. Client -> A.foo()
2. A -> B.callMe(A)
Now A continues execution and B starts doing callbacks on A:
3. a) A does something b) B -> A.configureStuff()
The callback from B to A returns and A still keeps doing something
4. A continues to do something
5. A returns to the client
Now, as I see it, if A is marked as isReentrant it is still in a running
transaction and therefore B is blocked when calling A (it is running in a
different thread, different VM or different machine). If A and B would be
running in the same thread then A would not continue execution and it would
work. However, the synchronization problem would then be completely up to
the developer of bean A, for all methods, since there is no way of
temporarily disabling the setting. Right?
Does anyone have a solution on how to do solve the blocking problem or an
explanation on how difficult it would be to synchronize A?
Thanks
/Kalle
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
