Hello there,
I’d like to trace all my Tuscany 1.6 components using aop. I’ve seen http://tuscany.apache.org/logging-tracing-and-timing-in-tuscany.html and understand that I need to provide the -javaagent VM parameter, a META-INF/aop.xml in every contribution and an Aspect implementation. I want the tracing output documented using my own Logging component (which is not itself traced), so I will need to provide my own Aspect class. At the moment, I have done nothing but provide start a component with -javaagent:${workspace_loc}\lib\aspectjweaver-1.6.1.jar, and immediately I get a lot of output to System.err with messages like info using configuration file:/C:/Programme/ApacheSoftwareFoundation/tuscany-sca-1.7-SNAPSHOT/lib/tuscany-sca-all-1.7-SNAPSHOT.jar!/META-INF/aop.xml info define aspect org.apache.tuscany.sca.aspectj.UserTimingAspect [RMIServiceClassLoader@19a61d3] warning no match for this type name: org.apache.tuscany.sca.aspectj.UserTimingAspect [Xlint:invalidAbsoluteTypeName] error Non-aspect types can only be specified in a declare precedence statement when subtypes are included. Non-aspect type is : org.apache.tuscany.sca.aspectj.UserTimingAspect It seems that Tuscany attempts to use its own aspects to trace/time Tuscany itself, which I do not want. So do I need to remove that particular aop.xml file from the Tuscany modules? And if it’s using its own aop.xml, why does it complain about non-matching types? I am a little confused. Is there an example showing how this might work? Sebastian
