ComponentEvent is placed after Asset so it should be enough to just use after:ComponentEvent and before:PageRender in that case.
You didn't do the same error that I did and put both constraints in the same string (eg. "after:ComponentEvent,before:PageRender")? The constraints-parameter is a String var-arg. /Joakim On Fri, Aug 24, 2012 at 9:02 PM, Michael Prescott <michael.r.presc...@gmail.com> wrote: > Okay, it works correctly if I specify the following constraints: > > after:Asset > after:ComponentEvent > before:PageRender > > (The semantics of this mystify me, it seems redundant. Given the order on > the graphic Joakim sent, I'd have thought that after:ComponentEvent or > before:PageRender would be sufficient, but apparently not. If anyone has a > fuller understanding, I'd love to hear it.) > > Q. How do you tell whether the request corresponds to a vanilla request to > render a page? > > (or) > > Q. How do you tell which page a component event corresponds to? > > When my dispatcher came before either Asset or ComponentEvent, the code > > PageRenderRequestParameters decode = > linkEncoder.decodePageRenderRequest(request); > > .. returns misleading results. > > Michael > > On 24 August 2012 14:52, Michael Prescott <michael.r.presc...@gmail.com>wrote: > >> Right. I don't want my dispatcher to interfere with asset requests, so >> presumably I don't want my dispatcher before Asset, no? >> >> >> On 24 August 2012 14:49, Joakim Olsson <joa...@unbound.se> wrote: >> >>> Asset is before PageRender. See the image at the bottom of >>> http://tapestry.apache.org/request-processing.html >>> >>> /Joakim >>> >>> >>> On Fri, Aug 24, 2012 at 8:45 PM, Michael Prescott >>> <michael.r.presc...@gmail.com> wrote: >>> > I don't know! I thought ordered configurations formed a linear >>> sequence, >>> > so all I had to do was say which one I wanted it immediately before. >>> > Supplying multiple constraints seems redundant, and possibly >>> > contradictory. (e.g. "before a, but after c"). >>> > >>> > I'll give that a shot, anyways. >>> > >>> > Michael >>> > >>> > On 24 August 2012 14:39, Thiago H de Paula Figueiredo < >>> thiag...@gmail.com>wrote: >>> > >>> >> On Fri, 24 Aug 2012 14:58:21 -0300, Michael Prescott < >>> >> michael.r.presc...@gmail.com> wrote: >>> >> >>> >> I'm configuring my dispatcher with this: >>> >>> >>> >>> configuration.add("PageAuth", pageAuth, "before:PageRender"); >>> >>> This tells Tapestry to put my pageAuth dispatcher.. *after* page >>> render? >>> >>> >>> >> >>> >> Oops, my bad. But your dispatcher should be added before the asset one >>> >> too, shouldn't it? >>> >> >>> >> configuration.add("PageAuth", pageAuth, "before:PageRender", >>> >> "before:Asset"); >>> >> >>> >> >>> >> -- >>> >> Thiago H. de Paula Figueiredo >>> >> >>> >> >>> ------------------------------**------------------------------**--------- >>> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org< >>> users-unsubscr...@tapestry.apache.org> >>> >> For additional commands, e-mail: users-h...@tapestry.apache.org >>> >> >>> >> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>> For additional commands, e-mail: users-h...@tapestry.apache.org >>> >>> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
