Am 23.11.2005 um 00:08 schrieb Dov Rosenberg:
Has anyone put together a comparison on how WO components and tapestry
components are similar or not?
I don't have a point by point comparison, but I'll try to give my 2
cent ;-)
1. Do Tapestry components provide the "server side" event model
like a WO
Component?
If I get you right, I think I can say "Yes". Tapestry is event driven
as WO is.
2. Can Tapestry components be built from other Tapestry components?
Is there
a limit to the number of layers?
Yes, you can combine components to new components. I dont't know know if
there is any limitation to the number of layers, but I assume that
there is
none. However, it'll get confusing from a certain depths of layers ;-)
3. Is there a similar Request-Response loop paradigm?
Again, a "Yes". From the faq:
http://jakarta.apache.org/tapestry/faq.html
Events will trigger in the following order:
• initialize()
• pageBeginRender() ("rewind")
• rewind of the form / setting of properties
• Deferred listeners (for Submit components)
• Form's listener
• pageEndRender() ("rewind")
• pageBeginRender() (normal)
• pageEndRender() (normal)
After all, Tapestry is very much like WebObjects and if you have any
experience
with WO, your first steps with Tapestry will be quite easy. Except
that there is
no WOBuilder, but everything else is in most cases better ;-)
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
