JR43375: CMVC 223573 - CORRECT THE EMPTY PAGE WHEN VIEWING STORE DETAILS AFTER SEARCHING BY POSTAL CODE IN THE SMARTPHONE STARTER STORE.

WebSphere Commerce Version 7.0.0.7 Fix Pack

APAR status

• Closed as program error.

Error description

• In the smartphone starter store, Android and iOS hybrid
  applications, after using the store locator to perform a search
  using postal code or using the GPS to find nearest store
  locations in the hybrid applications, clicking View Details in
  the store result list for a particular store will return a page
  where the content area is empty.
  

Local fix

• Performing a search by city name will allow the store details to
  be viewed.
  

Problem summary

• USERS AFFECTED:
  WebSphere Commerce users on v7.0 FEP5 who are using the
  smartphone starter store, Android hybrid sample application or
  iOS hybrid sample application.
  
  PROBLEM ABSTRACT:
  In the smartphone starter store, Android and iOS hybrid
  applications, after using the store locator to perform a search
  using postal code, or using the GPS to find nearest store
  locations, clicking View Details for a particular store will
  return an empty page.
  
  BUSINESS IMPACT:
  Customers are able to view store info in the results list after
  performing a store search using postal code, but clicking View
  Details for a particular store will return an empty page.
  
  RECOMMENDATION:
  The JSP fix can be implemented manually for the existing
  published smartphone starter store. If the affected file has
  been customized, the changes required in this fix must be merged
  with the customized code.
  
  The following are instructions for implementing the required
  change to the JSP code:
  
  1) Open the following file:
  For runtime:
  <WC_eardir>/Stores.war/<storedir>/mobile20/Snippets/StoreLocator
  /StoreInfo.jsp
  For toolkit:
  <WCDE_installdir>/Stores/WebContent/<storedir>/mobile20/Snippets
  /StoreLocator/StoreInfo.jsp
  
  2) Locate the following code snippet:
  <c:if test="${!empty geoCodeLatitude && !empty
  geoCodeLongitude}">
      <c:set var="maxItems"
  value="${storeLocatorResultMaxPageSize}" />
      <wcf:getData
  type="com.ibm.commerce.store.facade.datatypes.PhysicalStoreType[
  ]"
    var="physicalStores" varException="physicalStoreException"
  expressionBuilder="findPhysicalStoresFromGeoCode">
    <wcf:param name="accessProfile" value="IBM_Store_Details" />
     <wcf:param name="latitude" value="${geoCodeLatitude}" />
     <wcf:param name="longitude" value="${geoCodeLongitude}" />
    <c:if test="${!empty radiusSaved}">
     <wcf:param name="value" value="${radiusSaved}" />
    </c:if>
    <c:if test="${!empty uomSaved}">
     <wcf:param name="uom" value="${uomSaved}" />
    </c:if>
    <wcf:param name="maxStores" value="${maxItems}" />
      </wcf:getData>
  </c:if>
  
  3) Locate the expressionBuilder parameter in the wcf:getData tag
  in the code snippet:
  
  <wcf:getData
  type="com.ibm.commerce.store.facade.datatypes.PhysicalStoreType[
  ]"
    var="physicalStores" varException="physicalStoreException"
  expressionBuilder="findPhysicalStoresFromGeoCode">
  
  4) In the opening wcf:getData tag, replace the value for
  expressionBuilder with the following:
  
  <wcf:getData
  type="com.ibm.commerce.store.facade.datatypes.PhysicalStoreType[
  ]"
    var="physicalStores" varException="physicalStoreException"
  expressionBuilder="findStorePhysicalStoresFromGeoCode">
  
  5) Add a new <wcf:param> for storeId to the wcf:getData element:
  
  <wcf:param name="storeId" value="${storeId}" />
  
  6) After the changes, your code snippet should resemble the
  following:
  
  <c:if test="${!empty geoCodeLatitude && !empty
  geoCodeLongitude}">
      <c:set var="maxItems"
  value="${storeLocatorResultMaxPageSize}" />
      <wcf:getData
  type="com.ibm.commerce.store.facade.datatypes.PhysicalStoreType[
  ]"
        var="physicalStores" varException="physicalStoreException"
  expressionBuilder="findStorePhysicalStoresFromGeoCode">
        <wcf:param name="accessProfile" value="IBM_Store_Details"
  />
        <wcf:param name="storeId" value="${storeId}" />
        <wcf:param name="latitude" value="${geoCodeLatitude}" />
        <wcf:param name="longitude" value="${geoCodeLongitude}" />
        <c:if test="${!empty radiusSaved}">
         <wcf:param name="value" value="${radiusSaved}" />
        </c:if>
        <c:if test="${!empty uomSaved}">
         <wcf:param name="uom" value="${uomSaved}" />
        </c:if>
        <wcf:param name="maxStores" value="${maxItems}" />
      </wcf:getData>
  </c:if>
  
  4) Save the file.
  
  5) For runtime, update the affected files in your published
  store by following the WebSphere Application Server instructions
  for updating your application
  (http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp
  ?topic=/com.ibm.websphere.nd.doc/info/ae/ae/trun_app_upgrade.htm
  l).
  

Problem conclusion

• The smartphone starter store JSP has been updated to use the
  updated expression builder query with the additional storeId
  parameter to required to return the store details.
  -------------------------------------------------------------
  The latest available maintenance information can be obtained
  from the Recommended Fixes for WebSphere Commerce technote:
  http://www.ibm.com/support/docview.wss?rs=3046&uid=swg21261296
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WC BUS EDITION

• Fixed component ID

  5724I3800

Applicable component levels

• R700 PSY

     UP