> be predefined). You can choose to say that Tapestry is not really > component based because of this lack of feature if you like, others may > disagree.
A component to me is something that is decoupled enough for easy reuse, and probably achieves some fairly low level objective. Tapestry has that. But it doesn't seem as powerful as Swing, where you can dynamically assign a component to a parent container component, right? And that appears to be the issue. With this in mind, I can't see how you would make a CMS like mambo for example. In that you can assign components to different places on the page dynamically. Mambo achieves this all in script. Could there be a similar/better way to do this, but take some advantage of tapestry? John --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
