IBM Support

PK93469: Page Designer in Portlet project does not show files included wi th a relative path

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Page Designer in Portlet project does not show files included wi
    th relative path.
    Steps to reproduce in Rational Application Developer 7.5.3:
    A. New Dynamic Web Project 2.4, EAR 1.4, Targeting IBM Websphere
     Application Server 6.0
    1. Add facets:
    
    - Design time template support
    
    - Java Server faces
    
    2. Create two JSP Fragments inside a WebContent\fragments
    
    - f1.jspf
    
    - f2.jspf
    
    3. Create a Faces JSP in WebContent
    
    - BasePage.JSP
    
    4. Add a jsp:include and browse to f1.jspf. This creates a relat
    ive path
    in the include tag.
    
    5. Add a f:subview with inside a jsp:include and browse to f2.js
    pf. This
    creates a relative path in the include tag.
    
    
    
    Results: In the Page Designer I can see both fragments. OK.
    
    
    
    B. Create a new Portlet project for JSR 168 Portlets, of type, S
    truts,
    associated with IBM WebSphere Portal 6
    
    1. I add the facet:
    
    - Design time Page template support
    
    
    
    2. Doing New-?WebPage, the template for creating a Fragment is n
    ot
    available.
    
    
    
    3. Create a JSP inside a directory called WebContent\fragments
    
    
    
    4. Create another JSP inside WebContents
    
    
    
    5. Add a jsp:include and browse to WebContent\fragments\f1.jsp.
    
    from the properties View
    
    
    
    The path is stored as relative:
    
    
    
    ?jsp:include page=fragments/f1.jsp'??/jsp:include?
    
    
    
    Result:
    
    
    
    The Page designer does not show the fragment.
    
    
    
    Note: If you change the path to be absolute:
    
    
    
    ?jsp:include page=./fragments/f1.jsp'??/jsp:include?
    
    
    
    then page designer will show the path.
    

Local fix

Problem summary

  • jspf fragments when incuded in a JSP are not visualized in
    the page designer.
    

Problem conclusion

  • The path to the jspf fragments missed a check to see if they
    need to be expanded during the link genration which has been
    fixed.
    
    Fix delivered in Rational Application Developer V7.5.4
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK93469

  • Reported component name

    RATL APP DEV WI

  • Reported component ID

    5724J1901

  • Reported release

    752

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-08-10

  • Closed date

    2009-09-25

  • Last modified date

    2009-09-25

  • 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

  • R752 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.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 September 2009