Hi Paul and all, Currently the output is logged directly in the console. Haven't looked into the capturing of parameter values but I think is a good idea.
Feedbacks welcome for further usability and improvement. Regards, James Yong On 2018/01/03 00:22:26, Paul Foxworthy <p...@cohsoft.com.au> wrote: > Hi James, > > I have been pondering something like this. > > I suggest the output should be in a structured format like XML, JSON or > YAML, so it can be parsed by tools. Maybe YAML because it's intended to > give wiki-like human readability. > > I suggest the ability to capture parameter values. You might make that > optional, with "summary" and "verbose" options. Parameter values would only > be logged if the "verbose" option is enabled. > > With both of these in place, one could use this to capture a series of > steps to generate a reproducible unit test, or to compose existing services > into a super-service. > > The minilang <trace> element and its implementation might have some > relevance. > > Cheers > > Paul Foxworthy > > > On 24 December 2017 at 03:37, James Yong <jamesy...@apache.org> wrote: > > > Hi All, > > > > Would like implement a feature to log a tree view of services, simple > > methods, events that are called during a request. > > Something like: > > -> Service A > > -> Simple Method B > > -> Service C (Async) > > -> Simple Method D > > > > All feedback is greatly appreciated. > > > > Regards, > > James Yong > > > > > > -- > Coherent Software Australia Pty Ltd > PO Box 2773 > Cheltenham Vic 3192 > Australia > > Phone: +61 3 9585 6788 > Web: http://www.coherentsoftware.com.au/ > Email: i...@coherentsoftware.com.au >
