you shouldn't have so many if at all utility classes in java as well
services should be used to compose process behavior not domain behavior IMHO
service -> enroll user
user -> domain behavior eg. concrete distinct action in responsibility of that domain object
I hate when people write code like this
get attributes of object
do something with attributes
set attributes back
instead having operation on object doing this and clearly encapsulate behavior and hopefully data as well
Comments
you shouldn't have so many if at all utility classes in java as well services should be used to compose process behavior not domain behavior IMHO service -> enroll user user -> domain behavior eg. concrete distinct action in responsibility of that domain object I hate when people write code like this get attributes of object do something with attributes set attributes back
instead having operation on object doing this and clearly encapsulate behavior and hopefully data as well