[jira] Resolved: (TUSCANY-2392) Enable debug tracing in Tuscany

["Dan Becker (JIRA)" <de...@tuscany.apache.org>]

     [ https://issues.apache.org/jira/browse/TUSCANY-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Becker resolved TUSCANY-2392.
---------------------------------

    Resolution: Fixed

It looks like between Raymond's prototype and the work done in Jira TUSCANY-2641 that this functionality has been covered. If there are additional requirements, let's open a new Jira and put in the specific issues that need to be addressed.

> Enable debug tracing in Tuscany
> -------------------------------
>
>                 Key: TUSCANY-2392
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2392
>             Project: Tuscany
>          Issue Type: Wish
>          Components: Build System
>            Reporter: Jean-Sebastien Delfino
>            Assignee: Raymond Feng
>             Fix For: Java-SCA-Next
>
>
> We've never really concluded the discussion on enabling some form of debug trace in Tuscany. Having built a number of samples, tutorials and applications with Tuscany, I think we need a way to trace through the runtime to understand when something goes wrong.
> I would like to see the following implemented:
> - direct calls to JDK logger (without an intermediate layer on top of JDK logger)
> - generated using aspectj
> - no hard dependency on aspectj in the Tuscany distribution, but instead steps describing how to enable it
> as already described here:
> http://marc.info/?l=tuscany-dev&m=118841084129220
> and demonstrated by Raymond there:
> http://svn.apache.org/repos/asf/incubator/tuscany/sandbox/rfeng/aop-logging/
> Disclaimer: this issue is not about monitoring which is a different subject and properly covered in the runtime at the moment IMO with the work that Simon and Ramkumar have done.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.