I think I will treat as a component each:
- at least one shared JAR of server related classes,
- at least one shared common JAR (for server and client),
- each JAR of each EJB,
- the ServiceLocator,
- the BusinessDelegates (depends on ServiceLocator)
- each Factory
- each WebCommand/Command pair
- each JSP or Servlet,
- the Java-client in total,
Originally posted by Leonardo Penha:
I am currently designing my component diagram, and I feel the ServiceLocator component is cluttering it. Every EJB dependency relationship has to use the service locator to lookup the bean. In my case I have 3 Session Facades plus a few other Entity Beans. If every EJB dependency needs a service locator then I have too many lines crossing each other in the diagram.
I was thinking about providing just one example of an EJB lookup via service locator in a separate component diagram and saying in my assumptions document that every EJB dependency relationship in the main component diagram uses the service locator.Would anyone think this is acceptable?