better method identification in AnnotationTransactionAttributeSource logging [SPR-11267] #15892
Labels
in: data
Issues in data modules (jdbc, orm, oxm, tx)
status: backported
An issue that has been backported to maintenance branches
type: enhancement
A general enhancement
Milestone
Thomas Whitmore opened SPR-11267 and commented
We am using
@Transactional
annotations in our projects, but logging does not identify the methods found very well.In our project there are many separate DAOs & services, which frequently use similar method-names. We see 400+ of these, a good proportion of which have repetitive names & without classes cannot be identified:
Adding transactional method 'findById' with attribute: PROPAGATION_REQUIRED,ISOLATION_DEFAULT,readOnly; ''
Adding transactional method 'remove' with attribute: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; ''
Adding transactional method 'create' with attribute: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; ''
Adding transactional method 'update' with attribute: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; ''
Adding transactional method 'findById' with attribute: PROPAGATION_REQUIRED,ISOLATION_DEFAULT,readOnly; ''
Adding transactional method 'create' with attribute: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; ''
Adding transactional method 'update' with attribute: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; ''
We want to be able to identify whether a particular class/method is getting scanned (or not) for transactionality, to allow us to engineer/ diagnose/ debug in this area.
Logging Class.Method would be much more useful (simple name only, no FQN) to enable engineering & diagnostis of transaction definitions.
(Keywords: AbstractFallbackTransactionAttributeSource, AnnotationTransactionAttributeSource, transaction attribute source logging, method name.)
Affects: 3.2.6
Issue Links:
Referenced from: commits 57eedf3, 82ea9ec
Backported to: 3.2.7
The text was updated successfully, but these errors were encountered: