Project

General

Profile

bug #8161

bug #8075: multiple cascase all-delete-orphan exceptions related to DefinedTermBase.representations

*FilterablePagingProvider classes as transactional readonly spring beans

Added by Andreas Kohlbecker 3 months ago. Updated 3 months ago.

Status:
Rejected
Priority:
Highest
Category:
cdm-vaadin
Target version:
-
Start date:
03/04/2019
Due date:
% Done:

0%

Severity:
critical
Found in Version:
Tags:

Description

Turing the TaxonNameStringFilterablePagingProvider into a readonly service bean should solve the cascade="all-delete-orphan" problems mentioned in #8075.
It would make a lot of sense to turn all the *FilterablePagingProvider classes into transactional readonly spring beans.

As prototype beans?


Related issues

Duplicated by Edit - bug #7945: TaxonNamePopupEditor: missing genus causes exception when updating name parts visibility Rejected 12/10/2018

Associated revisions

Revision 52aa37ab (diff)
Added by Andreas Kohlbecker 3 months ago

ref #8161 TaxonNameStringFilterablePagingProvider as transactional readonly prototype bean

History

#1 Updated by Andreas Kohlbecker 3 months ago

  • Subject changed from *FilterablePagingProvider classes as into transactional readonly spring beans to *FilterablePagingProvider classes as transactional readonly spring beans

#2 Updated by Andreas Kohlbecker 3 months ago

  • Duplicated by bug #7945: TaxonNamePopupEditor: missing genus causes exception when updating name parts visibility added

#3 Updated by Andreas Kohlbecker 3 months ago

  • Status changed from New to Rejected
  • Target version deleted (Release 5.6)

the *FilterablePagingProviders only are using service methods which are anyway annotated with @Transactional(readOnly=true), therefore it makes not much sense managing transactions in the *FilterablePagingProvider classes. - rejecting ticket

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)