Peter, I found that the best way of learning about how patterns are used in architecture and design was to read up on struts. There are many books (some free) and articles around on the net. Struts uses lots of patterns and it really helped me understand.
A lot of questions rising after a quick look at this pattern...
I guess we need a business delegate also for the swing client? There's not much sense in swing client talking to a servlet? Therefore is it a good idea to present a common business delegate component? (Between a servlet and a session facade and on the other hand between a swing client and the session facade?).
In Cades component diagrams, I would have a separate servlet for a client GUI. The servlet would act as a controller and Business Delegate. The Blueprints recommend having separate controllers for different clients.
Originally posted by Ramon Gill: Yes. A clue is that it uses a service locator to look up the session bean.
You often find components can be in many patterns. It is probably a singleton as well. Also is part of MVC.It would be nice if there were more comments in Cades diagams explaining these things.
I'm starting to doubt that Cade actually "implicitly" uses the business delegate pattern in his example. One reason is that he has more than one controller in his example - CatalogController and OrderController. Wouldn't this defy the business delegate pattern which is a single point to put all necessary code for communicating with the business tier?
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop