Unlike any other classes in the CaveatEmptor, the category class is relative static during the course of the service. I think the data should be a part of system configuration, but not interface to a user, even those with administrator role. Any reasons it is presented in the fashion? I might miss something in this regard.

I've no idea what you say :)

What I try to say are followings:

1) Among of all class definitions, the User, Customer, Bid, BidDetails can be created, altered, deleted during the course of the application service.

2) The category is a pre-defined system level data. It is a read-only data for all users. It shoull not be created, changed, or deleted by any users under the normal circumstance.

I am curious about the existence of the findByExample, makePersistent, and makeTransient methods in the DAO class based on the above two points.


Hope I clarify myself this time.

Well, the Category can be changed in my application, so I need that DAO. I've no idea why I shouldn't modify item categories in an auction system, its a perfectly valid case.