• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Piet Souris
  • Carey Brown
  • Stephan van Hulst
Bartenders:
  • Frits Walraven
  • fred rosenberger
  • salvin francis

Is J2EE patterns based on specific version?

 
Ranch Hand
Posts: 129
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I looked the Transfer Object pattern at book Core J2EE Patterns, 2nd. It describes a "Entity Inherits Transfer Object Strategy". It should base on EJB 1.1 or earlier, but not for EJB 2.0. Is some J2EE patterns based on specific version?
 
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I guess so. Another example is composite entity pattern, which only applies to the EJB 2.0.
 
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The standard Gof pattern apply to J2EE as well.
There is no need to go too detail into J2EE pattern.

In J2EE you only need to understand,
1) MVC for Web tie.
2) Session facade for EJB
3) Value object for transfer data.

No need to learn about pattern about Entity bean, that thing really sucks, as far as I can remember, there was not any question about Entity bean pattern.
 
reply
    Bookmark Topic Watch Topic
  • New Topic