Correct. In order to integrate with the JSF navigation system, PrettyFaces must replace the “pretty:id2” value with “/page” before the link is rendered. After the link is rendered, PrettyFaces then attempts to perform outbound rewriting on “/link”, for which it finds mapping “id1”
However, we could actually do something a bit tricky here, and try to “embed” some metadata into the view-id if outbound rewriting is enabled, something like:
This would then be removed by prettyfaces when the outbound rewrite occurs in PrettyFacesWrappedResponse, resulting in:
However, I’m not really sure how safe this would be, since it is quite hack-ish.
Do you play Magic?
Get TopDecked MTG, the #1 Magic App, built by players, for players. Free to use, forever.