Migrate > Migrating WebSphere Commerce Developer > Migrating custom assets > ... non-EJB projects > ... store asset project

Migrate JSP files

Overview

There are significant differences in version 5.6.1 JSP files and the JSP files in v7. Migrating the JSP files is performed differently depending on what stores you are using.

To only use the new WebSphere Commerce v7.0 store, no action is required. If you are migrating from WebSphere Commerce v6, you can proceed directly to step 3 and copy the store properties files to the version 7 installation.

Procedure

1. V5.6: To use only the original store:

   1. Open WebSphere Commerce Developer v7.0. Open the Projects view.

   2. Select the store project and click WebContent > WEB-INF. Double click the web.xml file and the Deployment Descriptor editor opens.

   3. Click on Source typically located in the bottom of the Deployment Descriptor editor. The web.xml file is displayed.

   4. Search for the <jsp-config></jsp-config> section of the web.xml file and add the following information:

      <jsp-property-group> 
              <url-pattern>*.jsp</url-pattern> 
              <el-ignored>true</el-ignored> 
      </jsp-property-group> 
      

      For example:

      <jsp-config>
      
          <taglib>
              <taglib-uri>flow.tld</taglib-uri>
              <taglib-location>/WEB-INF/flow.tld</taglib-location>
          </taglib>
            
          <jsp-property-group> 
              <url-pattern>*.jsp</url-pattern>
              <el-ignored>true</el-ignored> 
          </jsp-property-group>
      
      </jsp-config>
      

   5. Save the file and exit.

2. V5.6: To use the original store and a WebSphere Commerce v7.0 store concurrently:

   1. Conduct a global search and replace on the old store's JSP files and update the new taglib path from:

      <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %>
      <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %>
      

      to

      <%@ taglib uri="http://java.sun.com/jsp/jstl/fmt" prefix="fmt" %>
      <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
      

   2. Disable the JSP 2.0 EL support and use the JSTL 1.0 EL support, by performing the following steps:

      1. Open WebSphere Commerce Developer v7.0 and open the Project Explorer view.

      2. Select the store project and click WebContent > WEB-INF. Double-click the web.xml file and the Deployment Descriptor editor opens.

      3. Click on Source typically located in the bottom of the Deployment Descriptor editor. The web.xml file is displayed.

      4. If the section exists, remove from the web.xml file:

                
         <jsp-property-group>
             <url-pattern>*.jsp</url-pattern>
             <el-ignored>true</el-ignored>
         </jsp-property-group>
         

      5. Save the file and exit.

      6. Update the JSP pages. For further instructions on updating the JSP files, download the JSTL 1.1 specification and follow the instructions in Compatibility & Migration > A2 Migrating to JSTL 1.1.

3. After you have migrated the JSP files, in order to get all of the store pages to work, do the following steps:

   1. Navigate to the following directory on the WebSphere Commerce v5.6.1 or 6.0 machine:

      • WCDE_installdir\properties\tools\stores\store_name

   2. Copy the directory and paste it into the WebSphere Commerce v7.0 directory:

      • workspace_dir\WC\properties\tools\stores\store_name

   3. V5.6: Navigate to the following directory on the WebSphere Commerce v5.6.1 machine:

      • workspace_dir\Stores\Web Content\WEB-INF\classes\store_name

   4. V5.6: Copy the directory and paste it into the WebSphere Commerce v7.0 directory:

      • workspace_dir\stores\src\store_name

   5. Refresh the workspace and restart the server, if it was started.

Previous topic:

Migrate custom projects

+

Search Tips   |   Advanced Search