JR55466: Cannot use a custom view to form the email body for email notifications

APAR status

• Closed as program error.

Error description

• If you use a custom view to form the email body for shopper
  email notifications, REST calls inside JSP pages (which forms
  the mail content) are failing. For example, when the store
  invokes PurchaseOrderEmailNotificationView REST request, you
  might encounter an error similar to the following message:
  
  [2/3/16 12:32:09:284 IST] 0000019a ExceptionEnti >
  com.ibm.commerce.foundation.rest.providers.ExceptionEntityProvid
  er toResponse ENTRY java.lang.ClassCastException:
  com.ibm.commerce.messaging.programadapter.security.CredentialsSp
  ecifiedProgramAdapterSessionContextImpl incompatible with
  com.ibm.commerce.browseradapter.HttpSessionContext
  [2/3/16 12:32:09:287 IST] 0000019a ExceptionEnti 1
  com.ibm.commerce.foundation.rest.providers.ExceptionEntityProvid
  er toResponse java.lang.ClassCastException:
  com.ibm.commerce.messaging.programadapter.security.CredentialsSp
  ecifiedProgramAdapterSessionContextImpl incompatible with
  com.ibm.commerce.browseradapter.HttpSessionContext
      at
  com.ibm.commerce.foundation.rest.handlers.CommerceTokenRequestHa
  ndler.handleRequest(CommerceTokenRequestHandler.java:340)
  
  
  The issue occurs because WebSphere Commerce assumes that the
  session context is an HttpSessionContext in local binding, but
  that might not be the case every time.
  

Local fix

Problem summary

• USERS AFFECTED:
  WebSphere Commerce Version 7 Feature Pack 8 environments that
  use REST tags in the context of an email template or page
  container, running through local binding
  
  PROBLEM ABSTRACT:
  Cannot use a custom view to form the email body for email
  notifications
  
  BUSINESS IMPACT:
  Cannot use a custom view to form the email body.
  
  RECOMMENDATION:
  

Problem conclusion

• Wrapped retrieval of session context in local binding with a
  check to ensure that session context is an instance of
  HttpSessionContext before using session context. If it is not,
  the prefetched activity token will be used for the request.
  

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 DEV ED W

• Fixed component ID

  5724I3900

Applicable component levels

• R700 PSY

     UP