[MAGNOLIA-1335] commands: expose them as services Created: 01/Feb/07 Updated: 03/Dec/13 Resolved: 03/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Description |
|
I would be quite trivial and powerful to expose the commands as services. You pass the catalogue and command name to the service. All other parameters are exposed to the commands context. The command is executed. The service returns the exception (if set on the context), or the message if set, as we do in the workflow. This tool should include the browsing for the installed commands. This could be implemented by using a framework (http://xfire.codehaus.org) or by writing a simple servlet/page |
| Comments |
| Comment by Philipp Bärfuss [ 03/Dec/13 ] |
|
Possible since 5.2 |