Commerce Command Framework Important points to Remember

IBM WebSphere Commerce server commands follows specific design pattern that is  interface and implementation class. And every command will follow WebSphere command framework which implements command design pattern. It will do two main operations while implementing the command class.

• The ability to invoke an access control policy manager that determines if the user is allowed to invoke the command.
• The ability to execute a different command implementation for different stores, based upon the store identifier.

There are two ways to implement the command class.

• By declaring the implementation class in the interface.

Ex :String defaultCommandClassName = "com.ibm.commerce.member.commands.UserRegistrationCmdImpl";

• By declaring in the WebSphere Commerce command registry.

CMDREG table and its importance:

The precedence is given for the command registry. If nothing mentioned in the command registry then it will check for the default implementation mentioned int he interface.

If we have a extended sites model and if a command has two separate implementations for different sites,  then based on the storeId given in the CMDREG table the implementation class invokes.

If the command always use the same implementation its not necessary to mention it in the CMDREG table, rather we can define it in the interface as default implementation. But we cannot pass default parameters in interface declaration.

Read Full Info about Command framework