Data manager gets the data, controller does stuff to it (or the business logic is in the objects themselves). In Spring you can abstract out business logic like form validation as well.

I think it's fairly typical in these frameworks that the logic goes in the controller.

I should add, however, that we have a lot of business logic in the "model", ie. PL/SQL. I would agree to a certain extent with the poster in that logic that applies to the consistency of the model (which in some cases could be called business logic) belongs there, and logic pertaining to application flow belongs to the controller... however, application flow can be considered "business logic" as much as model consistency.

I think people get hung up on what has to go where, when they should be spending more time asking themselves, "where is the best place for this piece of code, regardless of what label I put on it".