A Session Facade + Value Object design patterns solves this problem
JaimeS
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855264#3855264
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3855264
ricardovm wrote :
|...
|ctx.getUserTransaction().begin();
|TestLocal t = home.findByPrimaryKey(id);
|...
|
LaLiLuna wrote : First I have a different proposal. Use a ValueObject design pattern
instead of calling all the getters. This is only one getter and you get a
First I have a different proposal. Use a ValueObject design pattern instead of calling
all the getters. This is only one getter and you get a class representing your entity
class. Change the class and send it back.
You can find the commit Options in
You probably need to update to commit option A etc...
in the default commit option, you application server does not assume he is the only
one touching the database therefore with every get you perform your app server
refreshes itself from the database in case anyone else updated the database.
dannyb23 wrote : You probably need to update to commit option A etc...
| in the default commit option, you application server does not assume he is the
only one touching the database therefore with every get you perform your app server
refreshes itself from the database in case anyone else
