[
https://issues.apache.org/struts/browse/WW-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44407#action_44407
]
Wes Wannemacher commented on WW-2723:
-------------------------------------
I agree with Musachy that dumping the ref rather than array values is ugly and
unhelpful, but I wonder how valuable it would be to add this to the core? Since
we support spring, why not just define pointcuts and advice on an action
if/when it becomes necessary to debug? Looking at Spring's config, it seems
that it would be easy to add pointcut/advice, build a logger and then when you
have what you want, you could take it back out.
I know that not all projects use Spring, but if it it truly necessary to find
out which action methods are being called, it might not be too much to ask to
add spring, and update the config.
-Wes
> Provide debug information about which methods where matched/invoked by OGNL
> ---------------------------------------------------------------------------
>
> Key: WW-2723
> URL: https://issues.apache.org/struts/browse/WW-2723
> Project: Struts 2
> Issue Type: Improvement
> Components: Expression Language
> Affects Versions: 2.0.11.2, 2.1.2
> Reporter: Jeromy Evans
> Priority: Minor
> Fix For: Future
>
>
> It would be helpful if developers could enable debug messages where Struts2
> displays the methods that were invoked when getting or setting a property.
> eg. rather than "user.firstName", see that it invoked action.getUser() then
> User.getFirstName()
> This will help debugging mismatched property names (eg. isUser(), getUser,
> getuser()) and especially help developers understand that, for example,
> getUser() must be invoked prior to setFirstName().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
