I came across it again, the LoggingService! Built into a framework for monitoring what actually happens in a web service setting, the LoggingService is intended to log incoming and outgoing data.
Why would you want to code cross-cutting concerns - aspects - in a "home-made service?"
In Java, you can use bytecode injection techniques to deal with aspects. In web services, use the application server's frameworks, or use web service agents, such as the AmberPoint product does.
But don't do it yourself, you will tie your code to a non-standard framework. Building your own LoggingService, the code using that service, must be hardcoded to use it. This tightly couples service implementations to the cross-cutting concern of logging and monitoring. This is not a good idea.