Good morning everyone. I'd like to seek a little advice from the community.
I've just spent a couple of days using Tapestry, and as a longtime WebObjects-user I'm feeling right at home with the Tapestry+Cayenne combination. I recently started working at a web development shop where most of the websites are run on an inhouse developed CMS which is very nice on the client side, but starting to show its age on the backend (J2EE/JSP). Tapestry looks like a great potential way for our future. Anyone care to give a quick comment on how to design a Tapestry-based structure for this use case? * About ~500 websites running in our CMS, each site a single web application. * In addition to the CMS, generic extensions that can be added (Shopping, Event scheduling etc). * Most sites include some custom components and logic. All in all, a pretty typical setup for a CMS/Web Development shop. So… Should I just declare the tapestry application package in the parent project (the CMS itself) and then create components/pages/additional services in that same package in my application project? Or do I have a better way of modualrizing the systems? Should I do something like this (http://tapestry.apache.org/component-libraries.html) for all the applications and extensions? Sorry if this is a FAQ—I'm still plowing through the documentation and mailing list archives to gain some familiarity with the framework. Cheers, - hugi --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
