title: Is POJO anti Object Orientation (OO)?
body: <p>In most definitions, POJO (Plain Old Java Object) is object with properties along with just getters/setters. Some people name these DTO. So essentially they are what i like to call them 'Data classes'. Whatever the name is i know there are these kind of objects where it just have getters/setters. And these are commonly used within developing multi-layered MVC web applications - where these objects would be passed through the different layers.</p>
  
  <p>Maybe my question is a bit towards opinionated - but is this pure OOP or not?
  I'm determined to find out the answer to this i.e. what's right and what's wrong?</p>
  
  <p>...Because, i have been brought up learning that OOP is all about modelling real-life scenarios/situations into objects through interaction. With objects themselves encapsulate data and behaviour which acts on this data. 
  - an object with just getters/setters doesn't fit into this definition in my opinion.</p>
  
  <p>Also, data classes are bad (code smell)  - that's what i've been taught in university.</p>