title: Java EE patterns -  Registry and others - relevance
body: <p>I am reading the book <a href="https://rads.stackoverflow.com/amzn/click/com/0321127420" rel="nofollow noreferrer" rel="nofollow noreferrer">Patterns of enterprise application architecture</a>. While going through the basic patterns - such as <a href="http://martinfowler.com/eaaCatalog/registry.html" rel="nofollow noreferrer">Registry pattern</a> I am finding that possibilities that these patterns which were first published in Nov,2002 may not be the best possible solutions to go for.</p>
  
  <p>For example take the Registry pattern. In our organization we use simple JDBC calls for db operations and if needed pass the connection object for a single transaction. This approach is not the best - but the alternative of using Registry pattern also <a href="http://www.brandonsavage.net/the-registry-pattern-reexamined/" rel="nofollow noreferrer">is not seeming good</a> as the dependency would then not be visible - can be an issue for testing. Dependency Injection is suggested as a better way to implement this behavior.</p>
  
  <p>Can anyone who has worked on Java EE web/enterprise apps comment on this - and what would you recommend to analyze the usage of each pattern (its pros and cons?).  Any recent book that does a coverage of this in detail?.</p>