Re: [Springframework-developer] Auto-wiring by type - too many instances when proxying?

[Rod J. <rod...@in...>]

>That's indeed a fairly typical scenario. I've considered 
this repeatedly, but haven't come to any conclusion 
yet. "Hiding" certain beans in a generic fashion is not as 
simple as it might seem: After all, at least the 
transactional proxy needs to reference its target, so the 
target can't be completely hidden.

Indeed it isn't simple. I've also thought about this. 

>Note that when auto-proxying targets, for example with 
BeanNameAutoProxyCreator, there's just one visible bean: The 
target automatically gets wrapped with a proxy. However, this 
is just appropriate for transaction demarcation if all your 
targets stick to the same method naming pattern; else, all 
those different transaction attributes in a single 
TransactionAttributeSource will get messy.
This is where attribute-driven transactions (with the advisor 
auto proxy creator) are attractive. The problem right now is 
that that means Commons Attributes slightly complicating the 
build process. JSR-175 will solve that one eventually, but of 
course it's too early to migrate most projects to 1.5 beta.

I want to do a JSR-175 preview integration with Spring, 
focused on attribute-driven transactions, as soon as I get 
time. (It's not a big piece of work.)

Rgds,
Rod