OK got it, thank you very much!
> 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. -- View this message in context: http://tapestry.1045711.n5.nabble.com/BeanModel-how-to-add-results-from-a-method-tp5717499p5717520.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
