IBM Support

PK77280: ?odc:tabbedPanel? references a WebSphere Portal class and cannot run on WebSphere Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the ?odc:tabbedPanel? component is used in a JSR-168 portle
    t, it assumes (and so requires) to be running in the WebSphere P
    ortal environment, as it references the WPS specific class: com.
    ibm.wps.pe.pc.std.core.PortletUtils
    
    The following exception occurs when running a JSR-168 JSF portle
    t on the WebSphere Application Server V7.0 JSR-168 portlet conta
    iner:
    
    com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E
    : Uncaught exception created in one of the service methods of th
    e servlet panelTest in application panelTestEAR. Exception creat
    ed : java.lang.NoClassDefFoundError: com.ibm.wps.pe.pc.std.core.
    PortletUtils
     at com.ibm.faces.bf.util.HttpRequestRetrieverForPortletJSR168.g
    etHttpServletRequest(HttpRequestRetrieverForPortletJSR168.java:2
    6)
     at com.ibm.faces.bf.util.ODCContextHelper.getODCPageContext(ODC
    ContextHelper.java:122)
     at com.ibm.faces.bf.renderkit.TabbedPanelRenderer.encodeEnd(Tab
    bedPanelRenderer.java:128)
     at com.ibm.faces.renderkit.DefaultAjaxRenderer.encodeEnd(Defaul
    tAjaxRenderer.java:83)
     at javax.faces.component.UIComponentBase.encodeEnd(UIComponentB
    ase.java:850)
      ...
    
    The problem can be worked around by placing a file named Odyssey
    BrowserFramework.properties in the root of the project's source
    folder with the following contents:
    
    REQUEST_CLASS=com.ibm.faces.bf.util.HttpRequestRetrieverForPortl
    et
    ECORE_FILES=
    EMAP_FILES=
    CLIENT_DEBUG_MODE=0
    CLIENT_LOG_LEVEL=-1
    SERVER_LOG_LEVEL=0
    MEDIATOR_DEBUG_MODE=0
    SERVER_LOG_FILENAME=
    PROGRESSBAR=0
    PATH_PREFIX=.ibmjsfres
    CLIENT_LOCALE=en
    

Local fix

Problem summary

  • Tabbed Panel component use a "request retriever" class to
    gain access to the underlying Http request object in portal.
    The request retriever it was using was not capable of
    handling non-WPS portlet containers. A different class is
    now used that can handle both WPS and WAS containers.
    

Problem conclusion

  • Fixed in Rational Application Developer V7.0.0.9 and V7.5.2
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK77280

  • Reported component name

    RATL APP DEV WI

  • Reported component ID

    5724J1901

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-12-10

  • Closed date

    2009-04-02

  • Last modified date

    2009-04-02

  • 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

    RATL APP DEV WI

  • Fixed component ID

    5724J1901

Applicable component levels

  • R750 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 April 2009