Comments on Regular Expressions: Logging Performance Exceptions (Part 1)

Oops. I neglected to mention that the source is a...

2008-03-18T19:15:00.000-07:00

Oops. I neglected to mention that the source is available for your abuse at http://hg.unreasonent.com/public/hatch-spring/.

Let there be aspects:http://www.unreasonent.com/so...

2008-03-18T19:10:00.000-07:00

Let there be aspects:

http://www.unreasonent.com/software/com.unreasonent.hatch/hatch-spring/

Repo root: http://maven.unreasonent.com/public/

Aspects would be a good way of doing this, however...

2008-03-17T10:11:00.000-07:00

Aspects would be a good way of doing this, however, it would also frequently be a harder sell to team-leads, etc. Adding one simple library and a few calls to it, would, I think, generally be seen as less invasive, so an easier sell to the team-lead if you needed to add some logging to help diagnose a production issue.

I agree AOP seems like a good fit for Hatch. I've ...

2008-03-16T12:39:00.000-07:00

I agree AOP seems like a good fit for Hatch. I've added an issue to experiment with this.

I like the simplicity of the current API; an average programmer can fit it in their head along with the original problem they're trying to solve.

A few years ago I wrote a similar performance moni...

2008-03-16T08:23:00.000-07:00

A few years ago I wrote a similar performance monitor thingy but I decided to use an aspect for it.

I think this kind of orthogonal concerns are better fitted in an aspect, as the logging code does not fit well in the methods you intend to monitor because it relates to a different level of abstraction.

Moreover you can apply you aspects to different methods by configuration