You could try this:
http://www.theserverside.com/patterns/ObserverPattern.jsp
or you could use JMS:
let Bean A notify Bean B of any state changes
so indirectly Bean A activates Bean B
How about this?
-----Urspr�ngliche Nachricht-----
Von: Sriphani Singaraju [mailto:[EMAIL PROTECTED]]
Gesendet: Do 24.01.2002 14:23
An: Fabian Crabus; [EMAIL PROTECTED]
Cc:
Betreff: RE: Re: Implementing wait in EJBs
Hi Fabian,
The scenario goes like this:
Bean B invokes a method on Bean A (B is ignorant of the state of A)
Bean B should try this repeatedly until the state of A is changed (to a state
favourable for servicing Bean B's request).
I know it is a performance overhead, but, thatz how the business logic goes.
For this case, I'm worried more abt achieving this rather than the amount of time Bean
B is blocked.
Hope this makes my point clear!
Regards,
Sriphani.
Any views expressed in this message are those of the individual
sender, except where the sender specifies and with authority,
states them to be the views of Huawei Technologies India Pvt. Ltd.
==========================================================================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".
