Hi, i was wondering what the "best practice" (best for you) for tapestry would be do define a common page layout for the whole web app and how to put the needed parts together... i mean i really loved (struts-)tiles (but not struts itself), as it is just wonderful in that way as it even can get its info from any RDBMs meaning it can be used to put things together even in CMS with ease... and i also would like to know how it could be (if its possible) done, to get the needed information for a whole site out of a DB - i mean an aproach similar to NUKES, where you dont have files holding data but a DB holds all content - i mean the aproch mark fleury took here http://www.onjava.com/pub/a/onjava/2003/06/04/nukes.html (e.g.: "As a real CMS engine, Nukes stores and manages the files you upload in a database. There is no file system with HTML files per se. This is a bit of a departure from the classical web site and a bit disturbing at first, but it turns out to be valuable as we build all kinds of fancy features on top of it. Your web site is stored in a database that makes it robust and easily versioned." ) - so far that even dynamic data comes out - eg. tapestry files out of the db ???
Regards, Korbinian PS: i already know the way Kent Tong did it in "Enjoying Webdevelopement With Tapestry 4" (Great Book!! - a shame that EU-citizens cant order it on hardpaper) - but i just like to know what other ways would work... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
