Hmm, I'm not sure it would be a great idea to introduce a new data format to OFBiz. It would mean adding new libraries to the framework and thus more complexity.
I know XML is not the greatest data format in the world, but it is what OFBiz uses, and so we should always try to stay consistent in our approach. On Wed, Jan 3, 2018 at 1:24 PM, Jacques Le Roux <jacques.le.r...@les7arts.com> wrote: > +1 for YAML > > Jacques > > > > Le 03/01/2018 à 01:22, Paul Foxworthy a écrit : >> >> 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 >>> >> >> >
