Re: Event before which request data is processed.

2010-09-03 Thread Michael Taylor
Yes thanks. I think that's exactly what I was looking for. On Fri, Sep 3, 2010 at 11:04 AM, Christian Gruber < christianedwardgru...@gmail.com> wrote: > Good answer! Thanks Thiago. Hadn't considered that. > > Christian. > > On Sep 3, 2010, at 10:02 AM, Thiago H. de Paula Figueiredo wrote: > >

Re: Event before which request data is processed.

2010-09-03 Thread Christian Gruber
Good answer! Thanks Thiago. Hadn't considered that. Christian. On Sep 3, 2010, at 10:02 AM, Thiago H. de Paula Figueiredo wrote: > On Fri, 03 Sep 2010 10:36:23 -0300, Michael Taylor > wrote: > >> Basically what we're trying to do is POST some data to our tapestry webapp >> from an external

Re: Event before which request data is processed.

2010-09-03 Thread Thiago H. de Paula Figueiredo
On Fri, 03 Sep 2010 10:36:23 -0300, Michael Taylor wrote: Basically what we're trying to do is POST some data to our tapestry webapp from an external application. What do you do after receiving the post? If it's just processing it then redirecting to another page, why don't you use a Dis

Re: Event before which request data is processed.

2010-09-03 Thread Michael Taylor
Basically what we're trying to do is POST some data to our tapestry webapp from an external application. Our initial thought was to do exactly as Igor suggested, make a page object, inject the HttpServletRequest and then read the post data from it. The implementation looked something like this pub

Re: Event before which request data is processed.

2010-09-02 Thread Thiago H. de Paula Figueiredo
Hi, guys! I stand corrected. :) On Thu, 02 Sep 2010 18:13:44 -0300, Howard Lewis Ship wrote: Thank you for pointing that out. I guess that the meaning has changed, it's more like "the page's persistent fields have been attached to the page instance for this thread/request". On Thu, Sep 2

Re: Event before which request data is processed.

2010-09-02 Thread Howard Lewis Ship
Thank you for pointing that out. I guess that the meaning has changed, it's more like "the page's persistent fields have been attached to the page instance for this thread/request". On Thu, Sep 2, 2010 at 2:07 PM, Igor Drobiazko wrote: > On Thu, Sep 2, 2010 at 10:55 PM, Thiago H. de Paula Figuei

Re: Event before which request data is processed.

2010-09-02 Thread Igor Drobiazko
On Thu, Sep 2, 2010 at 10:55 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > @PageDetached are ignored in Tapestry 5.2, as it doesn't use a page pool > anymore. > > That's not correct. The life cycle of a page is still the same: the page is attached to the request and detached wh

Re: Event before which request data is processed.

2010-09-02 Thread Thiago H. de Paula Figueiredo
On Thu, 02 Sep 2010 17:23:51 -0300, Christian Gruber wrote: Hey, Hi! We have a "page" we want to use roughly in place of writing a separate servlet that needs access to the request and all its raw data before processing for binding What do you mean by "before processing for bind

Re: Event before which request data is processed.

2010-09-02 Thread Igor Drobiazko
Just inject the Request [1] or HttpServletRequest (both are per-thread services) into your page and use it. [1] http://tapestry.apache.org/tapestry5.1/apidocs/org/apache/tapestry5/services/Request.html On Thu, Sep 2, 2010 at 10:23 PM, Christian Gruber wrote: > Hey, > > We have a "page" we wa