• 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:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Junilu Lacar
  • Rob Spoor
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Jesse Silverman
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Piet Souris
  • Frits Walraven

EE 5 and the killed j2ee patterns

 
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ranchers,

I'm working on assignment project (part II) and found that it would be nice to work with JEE 5. As I'm studing EJB 3.0 specification I learnt that there are patterns that no longer match with EJB 3.0 approach. Two of the most common patterns do not have any sense for me:

Transfer Object (TO): If you're using Java Persistence API (JPA) the entities are itself TOs, so an specific TO for that does not make any sense.

Service Locator: Well, it's hard for me to think of a service locator because it's quite easy to lookup ejbs (both remote and local) and we also no longer have the home interface... Any thoughts on this?

Thanks
 
Ranch Hand
Posts: 124
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have'nt had a chance to look at JavaEE5 yet, and yes I agree that it may call some patterns. However, it may not kill the two you stated.

TransferObject(Value Object): This pattern does'nt have a lot to do with entity beans. So even if you just had entities a Transfer object could strip down the data from the entity or at times combine the data from more than one entity and give the relevant data to the client. I dont see this pattern getting killed.

Service Locator: Once again this is used to locate services (EJB(s) or not). And more over this pattern gives clear seperation of concerns from the client who needs a particular service and the lookup involved in getting that service. So once again, I dont see this pattern getting killed.

Others who are familar with JavaEE5 may have a different opinion though.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic