Project

General

Profile

Actions

Defect #2230

closed

The processor new-node-processor is by default enabled

Added by Marek Klement about 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Marek Klement
Target version:
Start date:
04/24/2020
Due date:
% Done:

0%

Estimated time:
Affected versions:
Owner:

Description

The processor new-node-processor is by default enabled and should be disabled. Please add new property to disable it.


Related issues

Related to extras - Defect #2231: The processor new-node-processor is by default enabledClosedPeter Štrunc04/24/2020

Actions
Related to extras - Task #2331: Use isDefaultDisabled() for processorsClosedPeter Štrunc06/18/2020

Actions
Actions #1

Updated by Marek Klement about 4 years ago

  • Related to Defect #2231: The processor new-node-processor is by default enabled added
Actions #2

Updated by Marek Klement about 4 years ago

  • Status changed from In Progress to Needs feedback

Added to new branch and created pull request to 1.9.0-RC

Actions #3

Updated by Marek Klement about 4 years ago

  • Assignee changed from Marek Klement to Peter Štrunc
Actions #4

Updated by Radek Tomiška almost 4 years ago

Method EntityEventProcessor#isDefaultDisabled() could be used to disable processor by default. The benefit - it will work even when profile properties is not (or wrongly) configured.

Actions #5

Updated by Marek Klement almost 4 years ago

Thank you @tomiskar, I didn't know this was possible. I will adjust this here.

Actions #6

Updated by Marek Klement almost 4 years ago

  • Related to Task #2331: Use isDefaultDisabled() for processors added
Actions #7

Updated by Marek Klement almost 4 years ago

  • Status changed from Needs feedback to Closed
  • Assignee changed from Peter Štrunc to Marek Klement

Usage of isDefaultDisabled() will be done for all processors in extras in ticket #2331

Actions

Also available in: Atom PDF