[MGNLXAA-93] Do not send messages from activation Created: 23/Jul/15  Updated: 15/Apr/16  Resolved: 30/Jul/15

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: 2.3
Fix Version/s: 2.3.1

Type: Improvement Priority: Neutral
Reporter: Trang Truong Assignee: Espen Jervidalo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLACTIVATION-112 Do not send messages from activation Closed
relates to MGNLWORKFLOW-301 Publishers don't get error messages 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)
Date of First Response:
Sprint: Sprint 4 (Basel)
Story Points: 3

 Description   

Related to https://jira.magnolia-cms.com/browse/MGNLWORKFLOW-301.



 Comments   
Comment by Espen Jervidalo [ 24/Jul/15 ]

see linked workflow issue

Comment by Roman Kovařík [ 03/Aug/15 ]

Could we keep the old constructor to preserve binary compatibility?

Comment by Espen Jervidalo [ 03/Aug/15 ]

Yes. In case of Activation and XAA I will add the deprecated cunstructor.. In case of scheduler, that won't work, because of circular dependency.

Generated at Mon Feb 12 11:07:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.