Provide simple way of capturing repository invocation and its executing target.

[christophstrobl]

Currently there is no simple way for users to figure out which method is actually called via the RepositoryMethodInvoker since the class does not offer any kind of logging.

We should consider either adding straight forward logging statements (trace maybe) or enhancing RepositoryMethodInvocationListener.RepositoryMethodInvocation to include information, like the fragment type, about the target method.

The logger might be easier to understand as it does not require additional setup. RepositoryMethodInvocationListener is not well documented nor trivial to configure requiring a BeanPostProcessor.

Knowing the configuration we could also consider logging a report containing the method mappings once at startup.

[dongwooooooo]

Hi @christophstrobl is it okay if I take this issue?

[christophstrobl]

@dongwooooooo thanks for offering help with this one. Maybe another issue would be a better fit for your time since we already started to investigate what is possible and makes the most sense with the current arrangement. If you have ideas around this topic, please let us know or leave a comment on the issue brach, or PR once it's there.

[dongwooooooo]

Understood, I’ll step back on this one. Please feel free to tag me on anything else you think I could help with!