Hi I finally found some time to work on tapestry5 portlet 2.0 integration and i am so happy to do tweak Tapestry again.
By the way, I still feel uncomfortable with putting the whole Tapestry PATH in a single request parameter per portlet instance, as the existing contribution does. I feel like i'm missing something with all the tooling around portlets. The inherent concepts of Tapestry and portlet are so close, and at the same time so different in the implementation. Tapestry has only one Request Type when portlets provide a different type of request and response per type of request. Also portlet containers already implement some kind of "redirect after post" as tapestry does, so which one should i keep ? Here are just my confused thoughts :) Any hint ? -- Regards, Christophe Cordenier. Committer on Apache Tapestry 5 Co-creator of wooki @wookicentral.com
