CommandFactory.createCommand() method

This method searches the command registry(CMDREG table) for an entry corresponding to the specified command name (Interface)and storeId. if no entry is found for specified store, it will look for an entry corresponding to storeId=0. if both fail, it will check for a default implementation of the command from the interface and returns an entry that represent the default implementation of the interface.

Ex:

static final String defaultCommandClassName = "com.ibm.commerce.sample.commands.MyNewControllerCmdImpl";

so, when you make a command with the CommandFactory class, you need to pass in the interface name, rather than the implementation class, since the field looked up in the database is the CMDREG.INTERFACE field.

if you specify the implementation class (MyNewControllerCmdImpl) rather than the interface (MyNewControllerCmd) may result in a ClassNotFoundException.

Comments

Anonymous said…
In an extended sites model, is it preferred to define the commands using storeId=0 or repeat the definitions for each storeId that uses the command ? In theory, there can exist stores on the platform that might no use a shared command. Thoughts?
June 12, 2012 at 12:49 PM
Anonymous said…
Can i request you plz elaborate it.
June 12, 2012 at 8:28 PM
Post a Comment

Popular posts from this blog

Dataload Utility In WCS

Data can be loaded into WCS tables using data load utility.   WCS Data Load utility performs the following functions in a single operation: 1.              Reads the data from the input source file. 2.              Transforms the source data to WebSphere Commerce business objects. 3.              Allocates and resolves WebSphere Commerce business objects to physical data. 4.              Loads the physical data into the database. There are three configurations files and a input source file required to complete the data loader setup. WCS supports only CSV File Reader for other input source you have to write your own Reader Class. This means that if you are using OOB CSVReader then your input file must be a CSV file. The three config...
Read more

WebSphere Commerce

Image
1. Explain WCS Archetecture WebSphere Commerce functional architecture Descriptions: Controller layer The conductor of operations for a request. It controls the transaction scope and manages the session related information for the request. The controller first dispatches to a command and then calls the appropriate view processing logic to render the response. Presentation layer The presentation layer displays the result of command execution. The presentation layer can use JSP pages, or other rendering technologies. Business Context Service (BCS) A service that manages contextual information used by business components. The contexts include such information as globalization and entitlement. Business logic facade This generic interface is implemented as a stateless session bean which the controller calls to invoke controller commands. Controller commands A controller command business process logic such as...
Read more

10 Steps to Configure Email – Websphere Commerce Server

10 Steps to Configure Email – Websphere Commerce Server Websphere Commerce Server – Configure Email Follow 10 steps for configuring email in Websphere Commerce Server Step 1: Create a JSP ( eg:- AbcEmailNotify.jsp) Create a JSP, lets name it AbcEmailNotify.jsp AbcEmailNotify.jsp will be used for displaying contents of email to recipient. Note: Currently keep AbcEmailNotify.jsp as blank (without any code) Step 2: Create View ( eg- AbcEmailNotifyView) Make an Entry in Struts-Config.xml file for AbcEmailNotify.jsp as below < action path=’/AbcEmailNotifyView’ type=’com.ibm.commerce.struts.BaseAction’> < set-property property =’authenticate’ value =’10101:1′/> < set-property property =’https’ value =’10101:1′/> < /action> < forward name=”AbcEmailNotifyView /10101/-3″ path=”/< location of JSP file >/AbcEmailNotify.jsp” className=”com.ibm.commerce.struts.ECActionForward”> < set-property property=”implClassName” value=”com.i...
Read more