Sun indicated in an earlier e-mail to this list that they would be
integrating asynchronous messaging (distributed events) system into EJB in
the future. Obviously, we can't all wait for that to happen. It might be
interesting, however, to guess how Sun plans to integrate JMS into EJB.
I did a little research into JMS and the server side model of the
specification. I came to the tentative conclusion that a new bean will need
to be created in order for the specification to support asyncchronous
events. The new bean type, IMHO, would have one method that is activated by
an event. The context of the event would be available through a new
EJBContext type. This would make asynchronous beans as easy to develop as
servlets. I would be interested in anyone else's ideas on this.
Maybe it would look something like the following:
public interface AsynchronousBean extends EnterpriseBean {
public void processEvent( );
public void setAsynchronousContext(AsynchroniousContext ctx);
}
Obviously, this type of bean would be stateless.
===========================================================================
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".
