On Tue, 23 Feb 2010 17:14:22 -0300, Howard Lewis Ship <hlship@(protected)>
wrote:

> I agree that I'm a bit unhappy with the current API, but we now have a
> larger issue: backwards compatibility (from 5.1 to 5.2). We may
> eventually deprecate the current approach and create an improved
> approach and maintain both for one release.

We can keep the current API for incoming URLs and create another for
outgoing ones. Or create an ImprovedURLRewriteRule, extending
URLRewriteRule, that adds a Link rewrite(Link link) method. My original
plan was to provide the user the same way of dealing with incoming and
outgoing URLs, making it easier,, but now I see it wasn't a good idea. It
would even be simpler to implement the URL rewrite support with different
approaches for incoming and outgoing requests. :( My apologies.

--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)