I've been down this path. I liked tapestry from a development point of view, but had a problem with performance wrt Portlets. Basically, each Portlet has it's own Hivemind registry, so if you have 5 portlets on a page you get 5 x the initial performance hit for creating the portlet. If it's an instanceable portlet you get a registry for each instance. This makes adding portlets to a page an expensive operation (between 5-10s in my simple test app).
As a result we've stopped trying to use tapestry for portlet development. Judging from my reading of the list it doesn't look like many people are doing portlet development. John. ----- Original Message ---- From: Mitchell O'Brien <[EMAIL PROTECTED]> To: users@tapestry.apache.org Sent: Friday, 23 June, 2006 2:06:32 PM Subject: Portlets and Liferay? Hi all, my company is looking to create portlets for a project and I want to do this in Tapestry. We have already chosen a portlet container called Liferay and I was wondering if anybody has gotten Tapestry portlets to work with it and if there were any problems encountered? Cheers, Mitch --------------------------------------------------------------------- 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]
