[
https://issues.apache.org/jira/browse/WICKET-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899653#action_12899653
]
Igor Vaynberg commented on WICKET-2963:
---------------------------------------
we should be careful about the naming of these and make sure they are aligned
with how the core works. eg iirc the default mount mapper supports placeholder
${param} and indexed parameters but not the named parameters on the path
itself, only in the query string. so it looks to me like the
IndexedResourceMapper should actually be the default and the other one that
supports named parameters on the path should be named something else if we need
it at all.
> Add examples for the new request mappers in 1.5
> -----------------------------------------------
>
> Key: WICKET-2963
> URL: https://issues.apache.org/jira/browse/WICKET-2963
> Project: Wicket
> Issue Type: Wish
> Components: wicket-examples
> Affects Versions: 1.5-M1
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Attachments: resource-mappers.patch
>
>
> Add examples that demonstrate the new request mappers in Wicket 1.5.
> Such examples could be:
> * -custom mapper for the home page-
> * -custom mapper that uses the first url segment to encode/decode the session
> url-
> * fix the "Source code" URL for the example
> If you have an idea for more types please add them as a comment in this
> ticket.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
