Or we do need to have the Business Delegate even if it means just a layer containing the methods which calls the Session Facade to call the same methods?
Client --> Session Facade --> Application Service
Originally posted by Holden Caulfield:
There is something I really dont really like about my proposal: I dont like having all business methods on the Session Facade. I guess it could grow and grow and grow... On the other hand, I need it to force all method call pass throw it in order to manage the client session.
SCJP, SCEA
.. think of the FrontController, that is also the single point of access to a web-client. So I think it shouldn't be that bad. What do you think?
Originally posted by Holden Caulfield:
Hi Brian,
Client --> BusinessDelegate --> Service Locator --> Session Facade (SFSB) --> Application Service (SLSB)
Originally posted by Brian Smith:
Any reason to make Application Service as a SLSB?Why not just a POJO so that the business logic itself is not EJB dependent, more portable?
SCJP, SCEA
Originally posted by Holden Caulfield:
[
Well, dont know. In my opinion the frontController is quite different. It is true that it is the single point of access, but on the other hand it has not as many methods as my BusinessDelegate. I was thinking about a FrontController who resolves dynamically to which RequestProccesor/ActionProcessor/ActionCommand deliver the processing staff (like the mainServlet of the PetStore) What do you think?
SCJP, SCEA