Hi Chuck
Look at Publish-Subscribe Messaging. When multiple applications need to
receive the same messages, Publish-Subscribe Messaging is used. The central
concept in a Publish-Subscribe messaging system is the Topic. Multiple
Publishers may send messages to a Topic, and all Subscribers to that Topic
receive all the messages sent to that Topic. This model is extremely useful
when a group of applications want to notify each other of a particular
occurrence. See below for more.
warmest regards
Gopalan
______________________________________________________
Copyrights (c) Gopalan Suresh Raj, All rights reserved.
Visit me at my web site at http://www.execpc.com/~gopalan
----- Original Message -----
From: Chuck Zheng <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, September 19, 1999 6:05 PM
Subject: EJB & JMS
> Hello,
>
> I wish there is a JMS-INTEREST list to post this message.
>
> We are doing a EJB project with product supporting JMS as well, we will
> potentially employee JMS for at least following two tasks
>
> - perform event/alert notification from EJB server back to client PC.
> The driver is that there will be 2000 users of the system,
> some of them need to be notified of important event during server
> processing (business rule enforcement, etc) at real time. client
> polling is not acceptable Therefore we need a "callback" capability
> from EJB server to client
Sure. Your clients just need to implement the MessageListener interface and
subscribe to the Topic that they're interested in.
>
> - perform async calls from EJBean A to EJBean B & C. The driver is that
> A need to call B.foo() and C.bar() to collect info. The order of the
> call is not important, but B.foo & C.bar are slow in access DB. So we
> want to make async/non-blocking calls with B.foo and C.bar in parallel.
> B & C will notify A when they finish, so A can carry on with the rest
> of process. (Essentaily something similar to CORBA (Asynchronous
> Messaging Interface) AMI)
Same here too.Implement MessageListener interface and overload
onMessage(Message msg)
>
> I wonder which JMS mechanisms are suitable for these tasks. Has anyone
> come across similar problems?
>
> cheers
> chuck
>
>
===========================================================================
> 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".
>
===========================================================================
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".
