All geek questions in one place

Java EE patterns - registry and others - relevance

I am reading an Enterprise Application Architecture Templates book . Looking through basic templates such as the registry template , I find that features that were first published in November 2002 may not be the best possible solutions.

For example, take a registry template. In our organization, we use simple JDBC calls for db operations and, if necessary, pass the connection object for one transaction. This approach is not the best, but the alternative to using a registry template also does not seem good , since the dependency will not be visible then - there may be a problem for testing. Dependency injection is suggested as the best way to implement this behavior.

Can anyone who has worked on Java EE web / enterprise apps comment on this and that you would recommend analyzing the use of each template (its pros and cons?). Any recent book that details this?

+3
source share
1 answer

(...) Any recent book that details this?

I recommend Adam Bien Real World Java EE Patterns if you are looking for up-to-date coverage of patterns and best practices using Java EE 5 and 6:

Real World Java EE Patterns

Real-world Java EE Templates include:

  • An Introduction to Java EE 6 Fundamentals and APIs (EJB, JPA, JMS, JCA, JTA, Dependency Injection, Convention Configuration, Interceptors, REST)
  • , , Java EE 6
  • J2EE Java EE
  • , DAO, , , ..
  • -
  • ,
  • , , , Java EE 6 , Guice
  • Lean , ,
  • Java Connector Architecture (JCA)
  • EJB 2 - EJB 3
+2

Source: https://habr.com/ru/post/1765274/

More articles:


All Articles