[
https://issues.apache.org/jira/browse/OFBIZ-10351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284428#comment-17284428
]
Michael Brohl commented on OFBIZ-10351:
---------------------------------------
Hi James,
are those newer patches considering the valid feedback from Taher? I feel a
little uneasy to touch those core logic too, as this could also be a
performance issue doing all the checks for logging.
Considering the latest requirement to trace the service callstack (Danny
Trunk), what about writing some functionality which inspect the code from
outside, not during runtime. The code, eca, seca etc. could easily be parsed to
show how services are used in the codebase, maybe also with a nice html output.
This way we would have no runtime impact for a logic which, IMO, will not be
used that much.
> Tree View of Call Graph for Services and Simple Methods
> -------------------------------------------------------
>
> Key: OFBIZ-10351
> URL: https://issues.apache.org/jira/browse/OFBIZ-10351
> Project: OFBiz
> Issue Type: Improvement
> Components: base
> Affects Versions: Trunk
> Reporter: James Yong
> Assignee: James Yong
> Priority: Minor
> Fix For: Trunk
>
> Attachments: OFBIZ-10351.patch, OFBIZ-10351.patch, OFBIZ-10351.patch,
> OFBIZ-10351.patch, OFBIZ-10351.patch
>
>
> Option to log a tree view of services and simple methods, and events that are
> called in a request.
> Some discussion at
> https://lists.apache.org/thread.html/079455a596056334265ecbd410b4de13b6e61e1449ac258af5e9679b@%3Cdev.ofbiz.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
