Is it possible to deprecate the existing code without to remove it?
On Wed, Jun 2, 2010 at 7:11 PM, Howard Lewis Ship <[email protected]> wrote:
> I'm starting work on a replacement for the URLRewriter system. We've
> previously discussed this, and it will be a non-backwards compatible
> change (I'm starting by removing the existing URLRewriter and related
> code).
>
> The goals are:
>
> * Keep it simple.
> * Make it possible to easily rewrite the Links created for component
> event requests, page render requests, and asset requests.
>
> I think the basic API will be something like:
>
> public interface ComponentEventLinkTransformer {
> Link transformComponentEventLink(Link link,
> ComponentEventRequestParameters parameters);
> }
>
> In other words, contributed code has access to the same information as
> the ComponentEventLinkEncoder service (in fact, this will be invoked
> from inside CELE). There will be an ordered configuratoin
> of transformers. A transformer can return a non-null Link to replace
> the default Link.
>
> I have two main use cases:
>
> One client wants to easily prefix all Tapestry requests with the
> virtual folder "t5" (i.e., "/t5/somepage") to make it easier to run
> the T4 and T5 versions of the application side-by-side.
>
> A second client wants some specific control over URLs. They want a
> certain page to have a number of URLs that would normally map to the
> Index page instead map to this alternate page, with context.
> Obfuscated example: they want "/toys", "/games", and "/equipment" to
> all point to a Search page, each with a different page activation
> context. The short URL is important to them, but there's already an
> Index page at "/".
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Best regards,
Igor Drobiazko
http://tapestry5.de/blog
