[MGNLSCH-35] Contexts available to commands executed by CommandJob don't have access to the repository Created: 11/Jan/13 Updated: 19/May/22 Resolved: 19/May/22 |
|
| Status: | Closed |
| Project: | Scheduler |
| Component/s: | None |
| Affects Version/s: | 1.5.4 |
| Fix Version/s: | 1.5.x |
| Type: | Bug | Priority: | Critical |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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 |
|
When a command is executed via the scheduler, i.e by info.magnolia.module.scheduler.CommandJob, its context (passed to execute() or as MgnlContext.getInstance() don't have their repositoryStrategy set, resulting in an ugly NullPointerException. At the very least, this should not throw an NPE, but a more explicit exception. But I don't see there's a reason for this ? We can't have a user-specific context, but then why not pass the system context, rather than let developers believe they can use the given context, when really they can't ? |
| Comments |
| Comment by Roman Kovařík [ 19/May/22 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. Thank you, |