PM86812: Changing a JSF portlet page without a JSF action does not explain the JSR286 event scenario

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Abstract:
    
    The help topic Changing a JSF portlet page without a JSF action
    does not to explain the JSR286 event scenario
    
    Error Description:
    
    1. Create a JSR286 JSF 1.x portlet project, with two portlets
    with two jsp pages in portlet 1 and one in portlet 2
    2. Create a JSR286 creation code in portlet 2 and processing
    code in portlet 1
    3. Adjust the JSF getView method of portlet 1 as indicated in
    the help topic 'Changing a JSF portlet page without a JSF
    action' to return to jsp page 2
    4. Create two portal pages on Portal, each with one portlet
    5. Set connection between the portal pages: Enable global
    message on page with portlet 1, set connection to it from page
    with portlet 2
    6. In order to notice the problem, select portal page with
    portlet 1, trigger a JSF action in the portlet to go to jsp page
    2 of this portlet, trigger a JSF action go to jsp page 1 within
    portlet 1
    7. Switch to portal page with portlet 2 and trigger a JSF action
    to trigger a JSR286 event which gets processed by portlet 1 on
    the other portal page
    Expected Result:
    You should be on the jsp page 2 of the portlet 1
    Actual Result:
    You are on jsp page 1 even though getView returned the jsp page
    2
    
    Workaround:
    
    1. Add a navigation rule next to faces-config.xml pointing to
    /Test1Page2View.jsp
    2. Change the code of portlet 1 (assuming you use a JSR286 event
    named AnyMessage)
    if (event.getName().toString().equals('AnyMessage')) {
      response.setRenderParameter(REQUESTED_JSF_PAGE_KEY,
    '/Test1Page2View.jsp');
      NavigationHandler nav = facesContext.getApplication()
        .getNavigationHandler();
      String page = 'next';
      nav.handleNavigation(facesContext, null, page);
      facesContext.renderResponse();
      super.saveViewState(facesContext);
    }
    facesContext.release();
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The help topic Changing a JSF portlet page without a JSF
    action does not to explain the JSR286 event scenario
    

Problem conclusion

  • A new page titled 'Changing a JSF portlet page on processing
    events' has been added to describe the scenario.
    
    The fix for this APAR is included in the Rational
    Application Developer version 9.0 documentation.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM86812

  • Reported component name

    RATL SW ARCHITE

  • Reported component ID

    5725A3000

  • Reported release

    755

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-11

  • Closed date

    2013-07-11

  • Last modified date

    2013-07-11

  • 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

  • R755 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Rational Application Developer for WebSphere Software

Software version:

7.5.5

Reference #:

PM86812

Modified date:

2013-07-11

Translate my page

Machine Translation

Content navigation