One thing that confused me coming from WO to Tapestry was that I couldn't reuse components. In WO, you can have:
<webobject name="foo"></webobject> ... <webobject name="foo"></webobject> Translating to Tapestry: <span jwcid="foo"/> ... <span jwcid="foo"/> This is a no-no in Tapestry (at least in 3.x -- not sure if it has been fixed in 4.x). You have to duplicate the component specification in your .page (or .jwc) or use the copy-of syntax. And, of course, you have to give them different names. I'm not sure why a component/name can be reused in a loop, but not otherwise in your HTML. I'd prefer to only have to list it once, but that's not the way it seems to work. I'm guessing others have pretty much answered your other questions. /dev/mrg -----Original Message----- From: Dov Rosenberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 22, 2005 6:08 PM To: Tapestry users Subject: Tapestry Components versus WebObjects Components Has anyone put together a comparison on how WO components and tapestry components are similar or not? My primary concerns are the following: 1. Do Tapestry components provide the "server side" event model like a WO Component? 2. Can Tapestry components be built from other Tapestry components? Is there a limit to the number of layers? 3. Is there a similar Request-Response loop paradigm? I am pretty sure the answers to these questions is Yes. Any notes on the conversion would be appreciated. Thanks in advance -- Dov Rosenberg Conviveon/Inquira Knowledge Management Experts http://www.conviveon.com http://www.inquira.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
