It would because my own URLEncoder service would be based on the current Tapestry one, and in case the Tapestry one changes (bug, performance, whatever...) I would want to incorporate those changes also.
Context segments would be the segments in the context part of the URL, /a/b/c/. I have a solution that works using URLs like "app/page/type/1/3/6/9" and I think I will stick with that. Thank you for all your feedback. -----Original Message----- From: Thiago H de Paula Figueiredo [mailto:thiag...@gmail.com] Sent: 11. maj 2015 16:41 To: Tapestry users Subject: Re: Generate link to Tapestry page from another program On Wed, 06 May 2015 12:00:07 -0300, Poder, Jacob <jacob.po...@thermofisher.com> wrote: > I'll consider overriding the URLEncoder service, but I'm not too keen > on that as it will require me to check for changes in the std > implementation on each Tapestry upgrade. No, it won't. Why would it? > Maybe the most reliable solution is to use context segments after all... What do you mean by context segments? -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br --------------------------------------------------------------------- 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
