On 1/22/02 8:29 AM, "Aaron Smuts" <[EMAIL PROTECTED]> wrote:
> I was starting on some aspectj tracing stuff for JCS last night, but I > didn't get anywhere. > > Some standard timing and tracing stuff would be great. I'd like to be > able to build with timing on all methods or have some easy way to limit > to a certain set of classes. It would also be nice to be able to build > with the option to trace all method calls or log the parameters of > certain methods, or put in debug logging without messing up the code. . > . > Cool, well I'll check this stuff into turbine in a couple of minutes and then hopefully we can make a small library of aspects for tracing, timing, testing and debugging that we can share. I'm borrowing heavily from the the aj documentation but as we move forward we can get help from the aspectj users list. I think using aspects as part of the development cycle will definitely help with the process, and help us understand how aspects might be useful in production. What I'm checking in isn't all that general but I hope it will get us going. -- jvz. Jason van Zyl http://tambora.zenplex.org http://jakarta.apache.org/turbine http://jakarta.apache.org/velocity http://jakarta.apache.org/alexandria http://jakarta.apache.org/commons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
