Core entity class - should it maintain it's own state or should another class be used to maintain it's state?
up vote
0
down vote
favorite
I have a core entity class that I would be using in multiple places within our system.
As of now this entity class is just a property bag. I have another class which implements an interface, that contains all the logic for modifying the properties that reside in the core entity class. Is this good practice?
One of my colleagues told me that the entity class should maintain it's own state because all the logic to modify it's state will reside inside this class.
What are the pros and cons of the 2 approaches?
c# software-design
asked Nov 21 at 17:16
gtestasker
237
add a comment |
up vote
0
down vote
favorite
I have a core entity class that I would be using in multiple places within our system.
As of now this entity class is just a property bag. I have another class which implements an interface, that contains all the logic for modifying the properties that reside in the core entity class. Is this good practice?
One of my colleagues told me that the entity class should maintain it's own state because all the logic to modify it's state will reside inside this class.
What are the pros and cons of the 2 approaches?
c# software-design
asked Nov 21 at 17:16
gtestasker
237
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a core entity class that I would be using in multiple places within our system.
As of now this entity class is just a property bag. I have another class which implements an interface, that contains all the logic for modifying the properties that reside in the core entity class. Is this good practice?
One of my colleagues told me that the entity class should maintain it's own state because all the logic to modify it's state will reside inside this class.
What are the pros and cons of the 2 approaches?
c# software-design
asked Nov 21 at 17:16
gtestasker
237
I have a core entity class that I would be using in multiple places within our system.
As of now this entity class is just a property bag. I have another class which implements an interface, that contains all the logic for modifying the properties that reside in the core entity class. Is this good practice?
One of my colleagues told me that the entity class should maintain it's own state because all the logic to modify it's state will reside inside this class.
What are the pros and cons of the 2 approaches?
c# software-design
c# software-design
asked Nov 21 at 17:16
gtestasker
237
asked Nov 21 at 17:16
gtestasker
237
asked Nov 21 at 17:16
gtestasker
237
asked Nov 21 at 17:16
gtestasker
237
asked Nov 21 at 17:16
gtestasker
237
237
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53417411%2fcore-entity-class-should-it-maintain-its-own-state-or-should-another-class-be%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
