Peter, Neither is going to always be recommended over the other. A lot of it is preferences. Personally, I prefer property based access because it gives me the OO encapsulation. It's easier to develop that way up front than add it later.
Do note that you must use the same technique throughout your EJB. You can't use some field based and some property based.
Thank you Jeanne, but I thought that with field based access I received better encapsulation. Fields would be private, only entity manager could access them from outside. And I would write only necessary getters and setters for clients.
I am asking because I am about to start new project and there is no easy way to change my mind later.
Narendra Dhande
Ranch Hand
Joined: Dec 04, 2004
Posts: 950
posted
0
Hi,
In both the cases the fields would be private. You can put annotations either on field or property. It is personal choice.
One thing using the property based access, you can put extra logic in the method for validation purpose.
I can also put my validation logic in setters methods. Only entity manager can by pass this logic. But I suppose that on DB is everything OK. If not there is possibility to put this logic into entity listeners.
Originally posted by Peter Curila: Only entity manager can by pass this logic.
I like my test code to exercise as much of the code as the production code. Minimizing the difference in paths that the entity manager takes (through my code) helps achieve this.
0
