[
https://issues.apache.org/jira/browse/WICKET-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ertl updated WICKET-2963:
-------------------------------
Attachment: resource-mappers.patch
Ok, so uploaded the resource mappers again.
This time as a patch including pretty test cases. Mapping resources to custom
url's should be pretty common so I would really love to see this stuff go into
wicket core.
ResourceMapper:
map an url like
/segment-1/segment-2/${placeholder}/segment-4/named-param-key1/named-param-value1/...?query-key=query-value&...
to a resource. the relevant parts of the url will be put into the corresponding
PageParameters.
IndexedResourceMapper:
map an url like
/segment-1/segment-2/segment-3/indexed-param-0/indexed-param-0/...?named-param-key1=named-param-value1&...
to a resource. the relevant parts of the url will be put into the corresponding
PageParameters.
> 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.
