[jira] Updated: (TUSCANY-2641) Enhancements to Tuscany Logging and tracing

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

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

Dan Becker updated TUSCANY-2641:
--------------------------------

    Attachment: TUSCANY-2641.patch

Patch provides improvements to standard LoggingAspect and SimpleTracingAspect, logging of constructors and static initializers, a new TimingAspect that is configurable at runtime, etc.

> Enhancements to Tuscany Logging and tracing
> -------------------------------------------
>
>                 Key: TUSCANY-2641
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2641
>             Project: Tuscany
>          Issue Type: New Feature
>          Components: Java SCA Core Runtime
>         Environment: All
>            Reporter: Dan Becker
>         Attachments: TUSCANY-2641.patch
>
>
> As mentioned on the developer mailing list:
> Regarding the Tuscany "tracing-aspectj" module:
> 1) Break out some of the logging and trace pointcuts into the runtime configuration file (aop.xml). Currently the trace points are compiled into the module. Users must recompile to trace other than "* org.apache.tuscany.sca..*.*(..)" methods. It would be nice if this were in the config file. Then users interested in just one thing, say Java introspection, could change this to "org.apache.tuscany.sca.interfacedef.java.impl.*Introspection*", and this would take effect without recompiling.
> 2) Add a few pointcuts to look at constructors and static initializers.
> 3) Make a few explicit timing pointcuts and aspects for those who want to time certain Tuscany transactions, methods, or constructors. 

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