Identifying Message-Driven Beans in Enterprise Applications
Remote Procedure Call (RPC)-based communication, such as that employed by session beans, has the disadvantage that the sender must wait for a response. For instance, imagine that you invoke a business method on another session bean. You then need to wait for the method to return so you can undertake the next activity. What if the task you wanted to achieve was time-consuming and not particularly critical? Obviously, it would come down to a decision about how important the task really is and whether the performance impact is justifiable.
A message-based system, on the other hand, does not suffer from this drawback. So, in the same scenario, if the session bean were communicating with ...
Get Developing Enterprise Java Applications with J2EE™ and UML now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
