[MGNLOBS-26] NPE on running command triggered by event Created: 27/Jan/14  Updated: 06/May/14  Resolved: 06/May/14

Status: Closed
Project: Observation
Component/s: None
Affects Version/s: 2.0
Fix Version/s: 2.0.1

Type: Bug Priority: Critical
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLOBS-28 Repository property required in two p... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   
  • Enable activateAddedPages
  • add a page
  • outcome:
    • the first time the activate command will run fine
    • on second and subsequent attempts a NPE is thrown due to repository value being null. That is the command instance (the very same object [same hashcode] which worked the first time) is now no longer populated with the values from the config and has instead default values.


 Comments   
Comment by Federico Grilli [ 27/Jan/14 ]

Moved repository to command params so that it's kept across events.
The repository in the command params is also how it is actually configured in all other listener configs

Comment by Oliver Emke [ 04/Mar/14 ]

Does there a Migration-Task from Observer-Module 1.3.1 (Mgnl 4.5.x) to 2.0.x (Mgnl 5.x) exist?

Generated at Mon Feb 12 10:23:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.