p.s. My latest Tapestry accomplishment is having truly dynamically
generated components and pages. In other words, components are
generated at runtime from some of our custom database information. Try
that with JSP!
Sounds easy enough.
1. Rip functionality out of Tapestry. 2. Write custom taglib. 3. Use.
?
:)
Dream on! :))
You'd use a taglib in *what*? A JSP. Where does the JSP reside? In a WAR. So, you've already lost the comparison.
That siad, I need to look at Tapestry 2 to see if it is 'the one'.
Tapestry 1 fails for me as it's too hard to go beyond simple things. Not
that Struts/WebWork style 'MVC-2' is much better.
Tapestry 2? Version 3.0 is in release candidate stage at the moment.
Tapestry is all about making harder-to-do things much easier than any other web framework that I know. Tapestry is most comparable to Apple's (NeXT's) WebObjects if you are familiar with that.
Erik
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
