[
https://issues.apache.org/jira/browse/TAPESTRY-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAPESTRY-1564:
-------------------------------------------
Fix Version/s: 5.1
This would be very disruptive. I suspect it could be done, by letting
LinkFactory, PageRenderRequestDispatcher and ComponentEventRequestDispatcher
delegate to another service responsible for encoding stuff into URLs and
decomposing the URLs back.
> Pluggable strategy for mapping URLs to classes (and back)
> ---------------------------------------------------------
>
> Key: TAPESTRY-1564
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1564
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Environment: N/A
> Reporter: David Peterson
> Priority: Minor
> Fix For: 5.1
>
>
> It would be useful to be able to customise the URLs generated by and handled
> by Tapestry.
> For example, I would like to be able to map the URL "/article" to the
> ArticleViewer class, rather than having to create a page class called Article
> (which overlaps with the name of my model class).
> An alternative is to create a class in the package .../pages/view/ViewArticle
> and use the URL "/view/article". But this introduces an extra word into the
> URL which is ugly and also the number of slashes in a URL can affect the
> page's ranking in some search engines.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]