question about transaction interceptor

[Darren Shepherd]

The current impl of the transaction interceptor is that its placed on 
all public/protected methods of anything that extends GenericDaoBase. 
This means that a simple findX() call ends up going through that 
interceptor about 4 or more times as it goes through other methods likes 
searchIncludingRemoved, searchIncludingRemoved, createPartialSelectSql, etc.

Has it always been this way?  Or did the transition to spring introduce 
this.  The DB transaction interceptor code gets hit a lot.  I mean A 
LOT!  Good thing we have a JIT.

Darren