I have some questions about code organization. I have started my app by defining some business objects (which have no logic other than equals and hashcode) and creating a minimal T4 app to display them. I eventually want to use Trails so that I can annotate my existing business objects and create a backend as well as admin tools for modifying content. As I understand it, one should move the logic from Tapestry page classes into POJOs, but I don’t know what these POJOs should be called, if there should be one per page class or per BO, or where they should be located (ASO, hivemind service, spring service, etc.) especially with respect to Trails. Also, to what extent should business objects contain logic? What types of methods are appropriate? Should DAO calls go through the BO? What happens to the DAO in Trails? Okay, that last question is a little off-topic, but if anyone wants to share the answer, I’d be grateful.
I realize that this is a bit of a religious discussion, but I am knew to Tapestry development and still somewhat knew to Java web development, so any thoughts that you have on the subject would be appreciated. Thanks for your help, Rob -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.1/104 - Release Date: 9/16/2005
