IBM Support

PM48052: JSPWRITER HANDLED INCORRECTLY IN CASE OF TAG NESTING.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The JavaServer Page (JSP) generates code that fetches the JSP
    writer before doStartTag and doEndTag are called.  If the
    doStartTag method pushes a new writer or doEndTag method pops
    a writer,the fetched writer is not updated and subsequently
    markup is written to the incorrect writer.
    
    Sample:
    
    JSP code:
    
    <t:test name="div">
    This is some sample text
    </t:test>
    
    where t:test is a custom tag. In doStartTag this tag does a
    pageContext.pushBody(writer); to redirect the body to a custom
    writer and calls pageContext.popBody(); in doEndTag.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Version    *
    *                  8.0 users of JavaServer Pages (JSPs).       *
    ****************************************************************
    * PROBLEM DESCRIPTION: The JSP container fetches the           *
    *                      JspWriter before doStartTag() and       *
    *                      doEndTag() are called.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Since the JSP container fetches the JspWriter for a tag before
    doStartTag() is called, if doStartTag() does a
    pageContext.pushBody(writer) then the output of the tag will
    be written to the wrong JspWriter.   The same holds true when
    doEndTag() does a pageContext.popBody().
    

Problem conclusion

  • The JSP container was updated to fetch a tag's JspWriter after
    doStartTag() is called and again after doEndTag() is called.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.2.  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 number

    PM48052

  • Reported component name

    WAS EXPRESS

  • Reported component ID

    5724I6300

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-09-16

  • Closed date

    2011-10-17

  • Last modified date

    2011-10-28

  • 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

    WAS EXPRESS

  • Fixed component ID

    5724I6300

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7JFU","label":"WebSphere Application Server - Express"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021