On Thu, 01 Nov 2012 11:13:19 -0200, membersound <memberso...@web.de> wrote:
Why not? That would be perfectly good, even recommended, object-oriented
Because it was just an example here, I want to apply some calculations
for some rows, which should not clutter my entities. And of course
itself rely again on other entities, so the calculation is more a
process for a service than being directly placed in the entity object
itself.
For me, if some calculation or process can be done just by using the
fields of a given entity class, the method that does it should be in the
entity class. That's OOP. That's not clutter.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
