Defining Client Access with Interfaces
Defining Client Access with Interfaces
asynchronously. To avoid tying up server resources, do not to use blocking synchronous
receives in a server-side component, and in general JMS messages should not be sent or
received synchronously. To receive messages asynchronously, use a message-driven bean.
Because they have a different programming model, message-driven beans do not have
interfaces that define client access.
interface. The business interface defines the client's view of a bean. All other aspects of the bean
(method implementations and deployment settings) are hidden from the client.
Not only do clean interfaces shield the clients from any complexities in the EJB tier, but they
also allow the beans to change internally without affecting the clients. For example, if you
change a session bean from a stateless to a stateful session bean, you won't have to alter the
client code. But if you were to change the method definitions in the interfaces, then you might
have to modify the client code as well. Therefore, it is important that you design the interfaces
carefully to isolate your clients from possible changes in the beans.
required to, implement their business interface or interfaces.
access allowed by the enterprise beans: remote, local, or web service.
enterprise bean it accesses. (It is not required to run on a different JVM.)