Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Maybe it is obvious to you. I’m new to java (half year work) and I had a discussion with my collegues. I have troubles naming my classes according to their responsibilities. For that, my classes gain responsibilities they should never have.
Can you help me?
BTW: I’m working current at a project where I have to use a persistance-layer from service classes. I have split my packages to model, service and persistance.
There are certain patterns and guidelines behind these term, which is where I usually base it on:
Controller is based on the Model-View-Controller design pattern and should be used explicitly for the classes that implement the controller functionality based on this design pattern. E.g. if you are using Spring MVC and you extend from one of the Controller classes.
Service is a little less specific, but I recommend basing the implementation on the Service Layer pattern from “Patterns of Enterprise Application Architecture“. Basically where a controller is more platform specific (e.g. transport via HTTP and rendering of Hypertext, usually HTML for web based controllers) a service shouldn’t have to know about who is using it and how. You are just providing a uniform interface that can be used in turn by e.g. a web controller.
Managers well… manage stuff. Connections, application context, sessions; usually as a central location where components throughout the application can talk to.