As of today, the AOP based logging and tracing module (tracing-aspectj) is designed as an individual module, which can be attached with any SCA application by including the tracing-aspecj.jar in the classpath to enable logging and tracing for this individual application.
If the above said way is what we want, then not sure about the exact intention here. If any one has more information on the purpose of this module, please share the same. I believe, it would be ideal to configure the logging and tracing as policies. By this way the user would have more control on the enabling and disabling the tracing module. How exactly the policies will look like and how to implement the same is something that i am trying to investigate at this point of time. Please let me know your comments and suggestions. Thanks. On Thu, Jan 21, 2010 at 6:06 PM, Ramkumar R <[email protected]> wrote: > After gaining some understanding on the aspectj configuration and aspects, > able to > fix the existing issue under revision 901680. > > > On Wed, Jan 20, 2010 at 3:04 PM, Ramkumar R <[email protected]> wrote: > >> Looks like it never worked, as the org.apache.tuscany.sca. >> aspectj.UserTimingAspect class seems to be missing from 1.x source code as >> well. >> >> >> On Wed, Jan 20, 2010 at 2:50 PM, Simon Laws <[email protected]>wrote: >> >>> Interesting. Do you think it's never worked or is this just and >>> artifact of the move to 2.x? >>> >>> Simon >>> >> >> >> >> -- >> Thanks & Regards, >> Ramkumar Ramalingam >> > > > > -- > Thanks & Regards, > Ramkumar Ramalingam > -- Thanks & Regards, Ramkumar Ramalingam
