Forums Register Login

pojo / dto / entity beans

+Pie Number of slices to send: Send
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.
+Pie Number of slices to send: Send
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.
I have a knack for fixing things like this ... um ... sorry ... here is a consilitory tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 2206 times.
Similar Threads
SCEA 2/1 - Transfer Object Pattern question.
implementation strategy for a simple ordering application.
EJB3: when should session beans be used?
Domain Object Vs DTO....
EJB 2.0 and DTOs?
More...

All times above are in ranch (not your local) time.
The current ranch time is
Apr 16, 2024 04:23:39.