• 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
  • Tim Cooke
  • paul wheaton
  • Paul Clapham
  • Ron McLeod
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Roland Mueller
  • Piet Souris
Bartenders:

pojo / dto / entity beans

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am developing an application with ejb3.
I am not getting clear idea as i should go for entity beans to represent the persistent layer or should i go for pojo based layer? Is there any technical difference between pojo class behaviour and dto class behaviour?
Is it feasible to use separate hiberanate layer in ejb3 layer that can be used with hbmtoddl which can be used for pojo creation? Sorry for putting the different questions at the same place but this is my first post on javaranch and as these are related i am putting these at the same place.
 
Ranch Hand
Posts: 257
Hibernate Firefox Browser Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Cool,

See either select POJO or EJB.

First, EJB is a simple POJO wrapped with externel features provided by APPLICATION SERVER. If you want POJO based approach ( without extending all EJB realted classes) then use SPRING & HIBERANATE for your application.

The tradeoff between EJB & POJO depends on your application requirement.
reply
    Bookmark Topic Watch Topic
  • New Topic