On Thu, Mar 26, 2009 at 4:04 PM, dpark <[email protected]> wrote:

>
> Is this a job for a custom Service Encoder (friendly URL)?
>

This is presumably Tapestry 4.X, based on this reference (and past Exchange
Solutions experience)?

My guess is that you're better off with something like URLRewriter or, if
you're using Apache in front, doing some rewriting there.  A quick look at
Service Encoder makes it look like it'd be somewhat painful to accomplish
what you're looking for.  (Although someone with more ServiceEncoder
experience can feel free to contradict me).

  - Geoffrey
-- 
Geoffrey Wiseman
http://www.geoffreywiseman.ca/

Reply via email to