You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2012/10/24 14:54:12 UTC

[jira] [Commented] (WICKET-4835) Add debug log messages in CompoundRequestMapper#mapRequest

    [ https://issues.apache.org/jira/browse/WICKET-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483188#comment-13483188 ] 

Martin Grigorov commented on WICKET-4835:
-----------------------------------------

Since you have the sources around can you please attach a patch ?:-)
                
> 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
>
> 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