You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Christophe Cordenier <ch...@gmail.com> on 2011/09/19 14:11:55 UTC
Tapestry Request / Portlet Request
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
Re: Tapestry Request / Portlet Request
Posted by Jon Williams <wi...@gmail.com>.
Bring on the portlet tapestry. In version 5.4 is very exciting.
Keep rocking hard peeps
Jon
On Mon, Sep 19, 2011 at 6:54 AM, Christophe Cordenier <
christophe.cordenier@gmail.com> wrote:
> Of course, it can wait :)
>
> I'm mostly looking for advices and feedback, if any have some
>
> 2011/9/19 Howard Lewis Ship <hl...@gmail.com>
>
> > This should be deferred to 5.4 at this point. It is a welcome addition to
> > T5!
> >
> > On Mon, Sep 19, 2011 at 5:11 AM, Christophe Cordenier
> > <ch...@gmail.com> wrote:
> > > 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
> > >
> >
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator of Apache Tapestry
> >
> > The source for Tapestry training, mentoring and support. Contact me to
> > learn how I can get you up and productive in Tapestry fast!
> >
> > (971) 678-5210
> > http://howardlewisship.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
> --
> Regards,
> Christophe Cordenier.
>
> Committer on Apache Tapestry 5
> Co-creator of wooki @wookicentral.com
>
Re: Tapestry Request / Portlet Request
Posted by Christophe Cordenier <ch...@gmail.com>.
Of course, it can wait :)
I'm mostly looking for advices and feedback, if any have some
2011/9/19 Howard Lewis Ship <hl...@gmail.com>
> This should be deferred to 5.4 at this point. It is a welcome addition to
> T5!
>
> On Mon, Sep 19, 2011 at 5:11 AM, Christophe Cordenier
> <ch...@gmail.com> wrote:
> > 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
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Regards,
Christophe Cordenier.
Committer on Apache Tapestry 5
Co-creator of wooki @wookicentral.com
Re: Tapestry Request / Portlet Request
Posted by Howard Lewis Ship <hl...@gmail.com>.
This should be deferred to 5.4 at this point. It is a welcome addition to T5!
On Mon, Sep 19, 2011 at 5:11 AM, Christophe Cordenier
<ch...@gmail.com> wrote:
> 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
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org