Hi All Ranchers,
Thanks all for your support, I am working on part 2 and have a question about Dependency Injection in Business Delegate layer in a n Tier architecture.
(A) Is having jsp--->Managed Bean--->Business Delegate--->Service Locator--->Stateless Session Bean(Dependency Injection)---->Entity JPA acceptable in class and sequence diagrams?
(B) should I show a Business Delegate with Dependency Injection also like Stateless Session Bean injects for EntityManager? which means
jsp--->Managed Bean--->Business Delegate (Dependency Injection)--->Stateless Session Bean(Dependency Injection)---->Entity JPA in my diagrams?
Thanks so much for the response. If I go with (B), can a Business Delegate be used just to separate Presentation layer and Business Layer. Because I read on the sun website (link below) that Business Delegate hides lookup and access details of EJB architecture, does it mean that Business Delegate and Service Locator must go together? or can I just use it as a Presentation and Business layer separator?
I've used much simplier and straightforward solution (and passed):
JSF->Stateless Bean (dependency injcection)->JPA
The lookup is done by the server in dependency incjection, so I think there is no need for locators or business delegaetes.
For your follow-up question, yes, you can use Business Delegate as a separation between the presentation and business layer. There are different opinions on where to show the business delegate component in the Component diagram in part 2. I showed it in the presentation layer.