Customized views and URLs are not picked Technote
(troubleshooting)Problem(Abstract) You customizing WebSphere Commerce Scheduler or Messaging components to override a default URL or view. You must place the customized entry in the struts-config-ext.xml file, within the Stores Web module. The new configuration is correctly defined for the view or URL, store id, and device format. The new configuration is not picked up, and the default settings are still being applied by WebSphere Commerce. Cause Some default views or URLs are defined in the struts-cfg.xml from the Initialization Servlet Web module. These settings are loaded before the customized entries in the struts-config-ext.xml file from the Stores Web module. The Messaging and Scheduler components use the configuration from the Initialization Servlet Web module, if the view or URL is defined, before looking at the configuration in the Stores module. Resolving the problem Apply WebSphere Commerce Fix Pack 6.0.0.3 or higher. This fix pack includes a fix that removes customizable URLs and views from the Initialization Servlet Web module struts configuration files. Fix Pack 6.0.0.3 or newer is available from the WebSphere Commerce fixes by version page.
Cross Reference information
Segment Product Component Platform Version Edition Commerce WebSphere Commerce - Express Customization / Application Development i5/OS, Linux, Windows 6.0, 6.0.0.1, 6.0.0.2 Commerce WebSphere Commerce Professional Edition Customization / Application Development AIX, i5/OS, Linux, Solaris, Windows 6.0, 6.0.0.1, 6.0.0.2 Commerce WebSphere Commerce Developer Enterprise Customization / Application Development Windows 6.0, 6.0.0.1, 6.0.0.2 Commerce WebSphere Commerce Developer Professional Edition Customization / Application Development Windows 6.0, 6.0.0.1, 6.0.0.2 Commerce WebSphere Commerce Developer Express Customization / Application Development Windows 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3
Document Information Current web document: http://www.ibm.com/support/docview.wss?uid=swg21260861