The term JEE is tossed around a lot because it covers the widest range of applications development in the enterprise and distributed environments.

JEE-specific Design patterns

     

The term JEE is tossed around a lot because it covers the widest range of applications development in the enterprise and distributed environments. Infact, the JEE modules and environment is still growing with a rapid pace. So, it is important to take advantage of the most efficient and effective strategies while re-factoring the existing projects and developing newer ones. These efficient and effective strategies in JEE scenario are known as the JEE-specific Design patterns.

JEE-specific design patterns identify the minimal set of known problems that application architecture should solve. These patterns are based on the experiences of the JEE community (involved with JEE development) to solve the problems. 
 
 
Classification of JEE Design Patterns :

1. in;margin-right:0in;margin-bottom:12.0pt;margin-left: 0in"> Business Tier Patterns
   These business tier patterns tackle problems occuring in an application resulting from the presentation tier accessing distributed business services, network performances degradation due to multiple calls between client and server, memory impact due to retrieval of a large list of data, and so on. The patterns demonstrated here focus on and solve design problems occuring in the middle tier of a J2EE application.
   
   Session Facade Design Pattern
   Service Locator Design Pattern
   Value List Handler Pattern

2. Presentation Tier Patterns
   The presentation tier patterns deal with the common problems occuring in the presentation layer such as - view management and navigation, processing of dynamic business data, efficiently accessing the read-only data, and so on. The patterns under this category focus on and solve design problems occuring in the presentation tier of a J2EE application for example : 
   
   Fast Lane Reader Pattern

3. Data Access Tier Patterns
   These data access tier patterns tackles best practices for an application accessing the database or the underlying persistence layer from the business tier. The patterns demonstrated here focus on and solve design problems occurring in the data tier of a J2EE application.
   
   Data Access Object Design Pattern

Related Tags for JEE-specific Design patterns:
c,  ide,  development,  application,  io,  sed,  distributed,  environment,  vi,  range,  enterprise,  applications,  id,  app,  to,  round,  sse,  erp,  e,  it,  des,  li,  use,  dev,  enter,  in,  rm,  m,  nt,  tr,  os,  ca,  os,  j,  es,  distribute,  over,  me,  pp,  cat,  env,  s,  term,  ee,  at,  oss,  is,  ir,  iron,  jee,  environments,  environments,  develop,  cover,  and,  ar,  str,  wid,  s,  s,  ri,  th,  st,  ati,  ap,  je,  ica,  ica,  pl,  pr,  nd,  on,  o

More Tutorials from this section

• Design Pattern
• Abstract Factory Pattern
• Adapter Pattern
• Behavioral Patterns
• Bridge Pattern
• Builder Pattern
• Categorizing Design Patterns
• Composite Pattern
• Creational Design Patterns
• Creational Patterns
• Design Patterns
• Factory Pattern
• Few of the familiar Design Patterns in Java
• Design Pattern
• Introduction to Design Pattern
• JEE-specific Design patterns
• The Prototype Pattern
• Relationship among Design patterns
• Singleton Pattern
• Structural Patterns