Project

General

Profile

Actions

bug #8161

closed

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

*FilterablePagingProvider classes as transactional readonly spring beans

Added by Andreas Kohlbecker almost 4 years ago. Updated almost 4 years ago.

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

0%

Estimated time:
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

Has duplicate EDIT - bug #7945: TaxonNamePopupEditor: missing genus causes exception when updating name parts visibilityRejectedAndreas Kohlbecker

Actions
Actions #1

Updated by Andreas Kohlbecker almost 4 years ago

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

Updated by Andreas Kohlbecker almost 4 years ago

  • Has duplicate bug #7945: TaxonNamePopupEditor: missing genus causes exception when updating name parts visibility added
Actions #3

Updated by Andreas Kohlbecker almost 4 years 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

Actions

Also available in: Atom PDF