PK31467: EJPPC0006E: PORTLET AND SERVLET NAMES MUST BE DIFFERENT

6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Solaris
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for HP-UX
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Linux
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for Linux
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Windows
6.1.0.7 WebSphere Application Server V6.1 Fix Pack 7 for AIX
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for AIX
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for i5/OS
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for i5/OS
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for HP-UX
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for Windows
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for Solaris
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris

APAR status

• Closed as program error.

Error description

• EJPPC0006E: Portlet and Servlet names must be different within
  portlet.xml and web.xml
  
  Apparently Portlet COntainer has constraints against a portlet
  and a servlet having the same name within the same application
  ear file.
  
  Typical example:
  in helloportletapp, we have the following entries in web.xml and
  portlet.xml
  
  Portlet.xml
  
  ....
  
  ....
  
  <description>Hello Portlet</description>
  
          <portlet-name>HelloPortlet</portlet-name>
          <display-name>Hello Portlet</display-name>
  <portlet-class>com.peoplesoft.pt.portlet.hello.HelloPortlet</por
  tlet-cla
  ss>
  ...
  ...
  ...
  
  Web.xml
  
  ...
  ...
  ...
  
  <web-app>
      <description>Hello Portlet Application</description>
      <servlet>
          <servlet-name>HelloPortlet</servlet-name>
          <display-name>HelloPortlet Wrapper</display-name>
          <description>Automated generated Portlet
  Wrapper</description>
  <servlet-class>org.apache.pluto.core.PortletServlet</servlet-cla
  ss>
  
  ...
  ...
  ...
  
  When app is deployed, one gets the following error, hence the
  deployment fails.
  
  EJPPC0006E: Portlet and Servlet names must be different within
  portlet.xml and web.xml.
  

Local fix

• Suggested that Customer rename their servlet to something else.
  Customer has not returned with the status of the suggested
  change. I believe it should work.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: WebSphere Application Server version 6.1     *
  *                 administrators installing portlet            *
  *                 applications                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: Portlet applications cannot be          *
  *                      installed if portlets have the same     *
  *                      name as servlets                        *
  ****************************************************************
  * RECOMMENDATION: It is recommended to rename portlets to      *
  *                 not having the same name as servlets.        *
  ****************************************************************
  When URL addressability is enabled, portlet names must not be
  the same as any servlet in the same web application. If URL
  Addressability is not needed, this name requierement is not
  needed. A fix is required to switch off name validation if URL
  addressability is disabled.
  

Problem conclusion

• When URL addressability is disabled, the validation test if port
  let names match servlet names must also be disabled.
  With this fix and URL addressability disabled, a portlet applica
  tion can be installed also if having the same portlet name as a
  servlet.
  
  The fix for this APAR is currently targeted for inclusion
  in fixpack 6.1.0.5.
  Please refer to the recommended updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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:

Modules/Macros

• PORTLET
  

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP