Content deleted Content added
Shevonsilva (talk | contribs) ←Created page with ''''Business delegate''' is a Java EE design pattern. <ref name=":o_cjp">{{Cite web|url = http://www.oracle.com/technetwork/...' |
m clean up, typo(s) fixed: Follwing → Following, presentatoin → presentation, increses → increases, accessability → accessibility using AWB |
||
Line 1:
'''Business delegate''' is a [[Java Platform, Enterprise Edition|Java EE]] design pattern.
<ref name=":o_cjp">{{Cite web|url = http://www.oracle.com/technetwork/java/businessdelegate-137562.html|title = Core J2EE Patterns - Business Delegate|date = |accessdate = 22 June 2016|website = Oracle|publisher = Oracle|last = |first = }}</ref> This pattern is directing to reduce the [[Coupling (computer programming)|coupling]] in between business serives and the connected presentation-tier, and to hide the implementation details of services (including lookup and
==Structure==
Requests to access underlying business services are sent from clients, and lookup services are used by business delegates to locate the business service components.<ref name=":o_cjp"/>
===Components===
Basic components are Business delegate, Lookup service and business service.
====Business delegate====
Control and protection are provided through business delegate which can have two types of constructures, without ID and with ID, where
ID is a string version of the reference to a remote object such as EJBHome or EJBObject.<ref name=":o_cjp"/>
====Lookup Service====
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.<ref name=":o_cjp"/>
====Business Service====
This a business-tier component, such as an enterprise bean or a JMS component, which provides the required service to the client.
==Consequences==
Line 18 ⟶ 22:
* More flexibility and maintanability as intermediate business delegate layer decouples the business layer from the presentation layer.
* Business delegate exposes a uniform API to the
==Concerns==
* Maintenance due the extra layer that
* Business delegate should take care of the changes of the remote business object interfaces, and these types of changes are rare.<ref name=":pjeesp"/>
Line 30 ⟶ 34:
Resource Delegate:
<Source lang="java">
public class ResourceDelegate {
Line 141 ⟶ 144:
Remote interface for ResouceSession:
<source lang="java">
public class ResourceDelegate {
Line 259 ⟶ 261:
{{Design Patterns Patterns}}
[[Category:Software design patterns]]
|