Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • Sometimes you have classes, which represent the business logic, providing simple public API and hiding implementation details (be it inside the public methods or private ones), sometimes you have classes, which represent the data and are passed around in your application, which provide getters. Getters and Setters are Evil cannot and will not apply to everything. My prefered way is to have the POJO with public properties and pass it to processors which know what to do with the data. Because when I want a XML representation, I don't care about Monitor and vice versa. Commented Dec 7, 2015 at 10:22
  • 6
    I am surprised by the "duplicate" tag. The two questions seem only superficially similar (they both question the Single Responsibility principle, I guess). My question is about representations and information hiding. Commented Dec 8, 2015 at 11:13
  • 2
    @firtydank: I agree, there are some people here who press the "close as dupe" button a little bit too quickly for my taste. I am voting for reopening. Commented Dec 8, 2015 at 11:36
  • What is the difference between the object itself and the "POJO representation"? Commented Dec 8, 2015 at 20:29
  • @Aaron - the monitor application has its own API which uses a different object domain. Commented Dec 9, 2015 at 7:30