PM85674: Page Designer changes all JSP files with same template when a modification occurs

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Abstract:
    
    Attempts to change the context root of a web 2.3 struts 1.1
    project, followed by a refactor of the web project name, and
    then making a simple edit change to a JSP causes the Page
    Designer to invoke a build that causes all JSP files using same
    template to be changed.
    
    Problem:
    
    You change the context root of a struts application, followed by
    refactoring the project name and you notice that after you make
    a modification to a JSP using Page Designer that the template
    links are modified in all JSP files that use the same template.
    
    This actually has nothing to do with the refactoring or struts.
    You could have imported a simpler non-struts WAR, opened the JSP
    file and changed one character and saved. Page Designer (PD)
    would then kick off a builder (not related to context root or
    refactoring). The builder puts the template into the JSP.  Part
    of that process is fixing up links.  A template may be used by
    many JSPs in many different folders/locations.  Therefore, PD
    tries to fix it up for each JSP.
    
    
    Local fix:
    
    There is no known workaround at this time.
    

Local fix

Problem summary

  • Starting with version 8.0, two new options were introduced for
    handling links from design-time templates into web pages.  Those
     new preferences are
    locate in the group "Default Link path when design-time template
    is applied" on the preference page Window > Preferences > Web >
    Page Template > Links for Page.
    
    When you apply a design-time template to a Web Page the link
    contributed by template will be made either:
    ( ) Relative to document root directory
    ( ) Relative to document directory
    
    By default "( ) Relative to document root directory" is the
    behaviour applied.
    
    Either option re-works links in web pages from design-time
    templates having
    differences between version 6.x/7.x and 8.x.; For example,
    
    from
    
    <li><a href="/link/">A Link
    
    to
    
    <li><a href="/contextRoot/link/">A link
    

Problem conclusion

  • The fix for this APAR introduces a new option named "The same as
     template's links (unchanged)" on the "Default Link path when
    design-time template is applied" group.
    
    By selecting this new option links from design-time templates
    are not modified in web pages.
    
    The fix for this APAR is included in Rational Application
    Developer v8.0.4.3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM85674

  • Reported component name

    RATL APP DEV WI

  • Reported component ID

    5724J1901

  • Reported release

    804

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-26

  • Closed date

    2013-10-28

  • Last modified date

    2013-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

    RATL APP DEV WI

  • Fixed component ID

    5724J1901

Applicable component levels

  • R804 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Rational Application Developer for WebSphere Software

Software version:

8.0.4

Reference #:

PM85674

Modified date:

2013-10-28

Translate my page

Machine Translation

Content navigation