On Mon, 19 Sep 2011 09:11:55 -0300, Christophe Cordenier
<[email protected]> wrote:
Hi
Hi!
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.
I guess you're in the right track, trying to keep changes to a minimum.
I'd like to suggest you to create a branch, as this doesn't seem trivial
at all and it will make it easier for everyone to follow what's being done.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
