Business Delegate nothing but hiding the complexity of JNDI lookup.
Since our Model and Bean are at remote place, it will be registered with JNDI registry. Whoever wants to access this model has first to search it in the JNDI registry. If this searching of JNDI is written in the controller, we have to handle remote exceptions and other. And also we don't know whether the required model is at remote or local. Sometimes it can be local and sometimes it can be remote..
So all this stuff of coding we have to written in the controller. As per the design
pattern principle, cohesion is important/one of the priciple of design pattern..
Instead of writing all this in the controller, we will write it in a separate object..that is business delegate
By doing this: We are hiding the complexity of searching the JNDI in the controller and also it is well cohesive.. that is business delegate is designed for this particular task of searching the model in JNDI.
Micheal John
SCJP 1.4 (86%), SCWCD 1.4 (86%), SCBCD 1.3 (85%), SCDJWS (Just Started...) - Satisfaction Lies in Our EFFORT, Not in the ATTAINMENT