[
https://issues.apache.org/jira/browse/WICKET-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Parson updated WICKET-4835:
---------------------------------
Attachment: CompoundRequestMapper-debug-logging.patch
Patch for debug log messages in CompundRequestMapper (untested)
> Add debug log messages in CompoundRequestMapper#mapRequest
> ----------------------------------------------------------
>
> Key: WICKET-4835
> URL: https://issues.apache.org/jira/browse/WICKET-4835
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.0.0
> Reporter: Peter Parson
> Priority: Minor
> Labels: logging, mapping
> Attachments: CompoundRequestMapper-debug-logging.patch
>
>
> When there is need for very complex URL mappings it would be handy to have
> debug log messages written in CompoundRequestMapper#mapRequest(Request), e.g.
> logging mapperWithScore.toString() for all mappers having a score greater
> than 0.
> Currently, the best way to debug unexpected behavior with mappings is to
> attach the wicket sources, put a breakpoint after Collections.sort(list) and
> inspect the list using the IDE.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
