Jorg,
Thanks anyway for the suggestion. I've been away for a week, but it may
still come in handy :)
Right now, my biggest problem is that the Paginator seems to assume
request URIs of the pattern
"page(#)" - where # is the page number. I had overlooked the "page(#)"
pattern in the Howto.
Paginator generates links to other pages by searching for the current
page number in the URI and
replace the (#) with another number. My pipeline is triggered by a URI
containing a continuation,
so the paginator finds the current page number in the URI, as part of
this large integer (sigh). The
problems occur when the integer is the final digit in my continuation,
because the Paginator tries to
replace (<number>) while the final ")" is obviously beyond the length of
the String.
So, right now, my paginator is buried rather deep in my pipeline. I'll
have to reshuffle the whole
thing and the associated flowscripts to correct this :(
Sandor
Jorg Heymans wrote:
Sandor Spruit wrote:
It would also be a great help if somebody could explain what Paginator
does with the page numbering. It seems to fiddle with the URI to
fold-in references to other pages? It's kinda hard to see exactly what
happens, as my URI contains dozends of numbers (a continuation ID) :(
Unrelated, but if you don't like to see the continuation ID in the URL
you can pass it as a hidden param in the form and have a request param
matcher for it, like
<map:match type="request-parameter" pattern="continuation-id">
<map:call continuation="{1}"/>
</map:match>
and in the form template
<fi:continuation-id/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
