First I've heard of it. I didn't initially have plans on doing anything with it but I'd be happy to in order to save you from jsf. :)
Whatever "it" is probably won't happen in the initial alpha release as I have some other items taking higher priority, but if you start a jira issue with some clear parameters for me to test with we can probably figure something out. On 5/26/06, John Singleton <[EMAIL PROTECTED]> wrote:
I'm evaluating Tapestry, and facelets, for use in a Portlet based project. We need to migrate an exsiting Servlet/JSP based application to Portlets. Currently I'm leaning towards Tapestry, from a coding standpoint it seems much cleaner to me. The only problem is the initial overhead when adding a portlet to a page. I understand this is because creating the per Portlet instance of the Hivemind registry takes some time. My simple test portlet written in facelets adds to the page in about a second, but the tapestry version takes about 10. The customer probably won't stand for this. Is there anything I can do to reduce this initial hit? Is this something being addressed in 4.1 ? Thanks John --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
