Hi If we consider to add portlet support to Tapestry, the current Request object is maybe missing some methods. For example, let's say the developer want to answer an action request differently whether he is in a servlet or a portlet container, as we have isXHR() method maybe we should have a isPortletRequest() one.
I am trying to see the Portlet support as a contribution without modifying anything to the core, but i have the feeling that the Tapestry Request API must evolve too. If it stands as an external contribution, the developer will have contribution's imports in its page, so that he will not be able to re-use it in another context. I think slight changes in the request API may help to fill the gap between servlet request and portlet request, and the contribution will do the rest. Any idea ? -- Regards, Christophe Cordenier. Committer on Apache Tapestry 5 Co-creator of wooki @wookicentral.com
