[MGNLWORKFLOW-248] CommandWorkItemHandler works only with commands inside the default catalog Created: 28/May/14 Updated: 23/Mar/16 Resolved: 28/May/14 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | None |
| Affects Version/s: | 5.3.1 |
| Fix Version/s: | 5.4 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Espen Jervidalo |
| Resolution: | Duplicate | 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)
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
Root cause is CommandsManager:executeCommand(final String commandName, final Map<String, Object> params) This method's implementation does not fulfill its description: * Executes the given command by first looking in the default catalog. * Should the command not be found, it will try to look in all other * catalogs. it looks only in the default catalog, if the command is not found, an exception is thrown. |
| Comments |
| Comment by Espen Jervidalo [ 28/May/14 ] |
|
See linked ticket where you now can specify the catalog the same way the command name is passed. As a work around, you can use "catalog-commandname". Workaround will not work in 5.4 though |