cross-cutting-concerns

We are searching for an include mechanism for groovy scripts to have space for cross-cutting-concerns. In my example we have, web service endpoints as groovy scripts and want to log to our web service protocol. for that we use our implicit object (getting from our framework) to create the logging statement. But this is boilerplate code if we code this in every web service endpoint. We are searching for something like include() in php, that includes other groovy scripts, are there any ideas how to do this? Since you already mentioned “cross-cutting-concerns” I’d say that you need to intercept

(I originally asked this question in this comment , but Mark Seemann asked me to create a new question instead.) I'm starting a new app (.NET Core, if that matters), and right now I'm trying to decide how exactly to do logging. The general consensus seems to be that logging is a cross-cutting concern, so the logger shouldn't be injected directly into the class that is supposed to log. Often, there's an example like the following class how not to do it: public class BadExample : IExample { private readonly ILogger logger; public BadExample(ILogger logger) { this.logger = logger; } public void

What is a good example of a cross-cutting concern ? The medical record example on the wikipedia page seems incomplete to me. Specifically from this example, why would logging lead to code duplication ( scattering )? (Besides simple calls such as log("....") everywhere, which doesn't seem like a big deal). What is the difference between a core concern and a cross-cutting concern ? My end goal is to get a better understanding of AOP. Before understanding the Crosscutting Concern , we have to understand the Concern . A Concern is a term that refers to a part of the system divided on the basis of