title: MVC indirect associations
body: <p>I am talking about general MVC pattern which is explained on wiki. That nasty pink picture breaks me. I have seen different ones but the ones with indirect associations always puzzled me. <a href="http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller" rel="nofollow">http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller</a></p>
  
  <p>1 Why view has indirect association with controller?</p>
  
  <p>view is based on model - that is why the association is direct</p>
  
  <p>2 But why model has indirect association with a view? it doesn't even know about the existence of a view neither it needs to know?</p>
  
  <p>I develop with Java Servlets and Spring MVC and I am relatively new developer I have feeling that it goes back to past to other languages discussed by Martin Fowler. Because with Spring MVC I always use controller as a joining link with no weird indirect associations.</p>
  
  <p>I have started programming only 3 years ago, so I was always raised with ideas of doing things properly. For instance why would you store business logic in past in the model when it is completely wrong and inefficient if nowadays we combine MVC with n-tier where model is exactly what is - just a dumb class with parameters and getters+setters and the whole MVC just serve the UI as it was originally intended or was it not? We have DAOs and Service Layer encapsulating DAOS + some logic, how does it relate to model?</p>
  
  <p>My typical model is no more complex than a traditional 'Student' or 'Car' class typically resembling tables in database(I don't use ORM at the moment) Do I use it correctly? How does DTO relate to model?</p>