Hello everybody! First: I DON't think appfuse has any kind of problem, I've been in love with it since I found, and currently, I'm using equinox for my current project.
However, my manager, a very UML-Only person, has been questioning me about the java Beans, which represent my domain model. These are plain POJOS. I normally put any Business Logic in the Manager/Service class. He questioned why we dont have any Business rules in the domain object, and I have been unable to answer properly. Its just the way I've been doing it all along (bad answer I know!). Its also how I think appFuse manages it. So I started researching about it, and found the anemic domain modle, which basically states into "if you have domains model without behaviour, you're doing it wrong: its not OO programming, its procedural!". Do you any links or articles about why is it good to keep the business layer separated? Or is it now a good accepted practice to put logic in the domain objects? Thank you. -- View this message in context: http://www.nabble.com/Anemic-domain-model-in-appfuse--tp22335297s2369p22335297.html Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net For additional commands, e-mail: users-h...@appfuse.dev.java.net
