Mark,
>If you used some specialized in process service to deliver asynchronous
>notifications between EJB components, your components would be locked
>into a non-distributed solution and the EJB component model would be
>broken.
Deployment descriptor if i am right is made for deffering decisions like
this at deployment time whether to use JMS(out of process) or in-process
messaging.
Following is a solution, i can think of :
Containers since already maintain all instances, in a sense they are
listeners to all events generated by ejbs. Container can always have a
bulletain board where clients/ejb can express their interest in other
instances. Once event is generated, it will be propagated to the interested
party.
It will be great if this feature can be integrated in JMS that
differentiates between in-process and out-process.
This way we will not violate any ejb model.
Any thoughts.
Punit
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
===========================================================================
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".
