How do you structure your Tapestry app?

[mu...@fantasymail.de]

I was just wondering why Honeycomb creates a Core and a Web project for Tapestry....

To me a core is something that contains "Core" classes that can be reused in other Web projects....

However the created Core projects don't know anything about Tapestry, only the Web project...so you can only put Tapestry independent stuff in there.
To me classes baesd on PropertySelection etc...all belong to a reusable core....

So how do you all layout your Tapestry projects?

Put it all in one project or separation into 2 or 3 or 4 projects?

1. You could create one project for all your database objects that are project independent.

2. One for the Tapestry re-usable components that are project independent 

3. And finally your specific web project that makes use of all the reusable stuff? 

Or even 

4. a project to separate the project specific database objects from the Tapestry page and component classes?


Just curious....

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org