So I'm kinda new to EJB's but I know my way around Java. I'm developing an
application and would like to know whether it's suitable for the EJB
paradigm.
I won't go into details but in general I need to do the following.
(I'll explain it in terms of beans and you tell me if it can be done.)
There is one bean called the Registry. There are many other beans that
register
with this Registry in order to receive certain events.
The Registry bean receives events from clients and re-directs them to the
beans
signed up to receive the events
In short a Producer/Consumer model.
the Registry bean should be a singleton. (Is this possible with EJB's? I
think not...)
Beans can lookup other beans so the registration part should not be a
problem, but if every lookup creates a new instance of the Registry bean
then I'm SOL since I will not have a central place to match-up my beans with
the events.
I'm thinking an event bus would be useful here and implementing it in Java
is easy enough but I wanted to take advantage of the persistence and
scalability of the App server.
any input would be GREATLY appreciated.
thanks
-dom
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
