Requests to access underlying business services are sent from clients, and lookup services are used by business delegates to locate the business service components.5
Basic components are Business delegate, Lookup service and business service.
Control and protection are provided through business delegate which can have two types of structures, without ID and with ID, where ID is a string version of the reference to a remote object such as EJBHome or EJBObject.6
Business service is located by lookup service which is used by the business delegate. The implementation details of business service lookup is encapsulated by lookup service.7
This a business-tier component, such as an enterprise bean or a JMS component, which provides the required service to the client.8
Some consequences are as follows:
Following concerns can be considered:
A sample code for a Professional Services Application (PSA), where a Web-tier client needs to access a session bean that implements the session facade pattern, is provided below.
Resource Delegate:
12
"Core J2EE Patterns – Business Delegate". Oracle. Oracle. Retrieved 22 June 2016. http://www.oracle.com/technetwork/java/businessdelegate-137562.html ↩
Screening Technical Design Document – Version 2.0. Indiana, USA: Indiana state. p. 7. ↩
Kayal, D. (2008). Pro Java EE Spring Patterns. New York: Apress. pp. 161–166. https://archive.org/details/projavaeespringp00kaya ↩