You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Goal

  • To define new (more logical?) structure of where commands are implemented and defined.
  • Allow easier use of commands by the App developers.

Further (future) goals:

  • Better documentation (list of commands with description, and for each command a list of parameters).
  • Remove command pooling.
  • Allow commands to be injected.
  • Allow configuration-by-code for commands.

Current Status

The above class diagram represents the current distribution of the command classes into the (basic) packages. As we want to get rid of the Admin Interface module, we need to move the MessageCommand class and the whole tree of the BaseRepositoryCommand class to the another package(s).

Proposal

The command classes related to the activation (marked green on the above image) will be moved to the Activation module (package i.m.module.activation.commands), the rest will be moved to the Core module, to the i.m.commands.impl package.

 

  • No labels