PK77054: INCORRECT RENDERINGCONTEXT IN REMOTE RENDERING PORTLET (RRP)

APAR status

• Closed as program error.

Error description

• currentRenderingContext behaves differently in 6.0.1.1
  as compared to 6.0.1.4
  

Local fix

Problem summary

• Checking the fully qualified URLs in the remote rendering
  portlet and reusing the rendering context in a JSP can result in
  malformed URLs.
  

Problem conclusion

• When rendering content via the remote rendering portlet with
  fully qualified URLs enabled/selected the base
  (http://host:port) is appended to the  WCMServletPath.  In most
  situations this is not an issue however if a JSP is referenced
  in either the content, presentation template, etc and it uses
  the current RenderingContext to render some component or item
  then the URL ends up like:
  httphttp//host:porthttp//host:port/wps/wcm/myconnecthttp://host:
  port/wps/wcm/myconnecthttp://host:port. . . .
  ..
  Base is added to the WCMServletPath by the remote rendering
  portlet when fully qualified URLs is selected.  Therefore when
  the rendering context is captured and used in a JSP to rendering
  something with workspace.render the URLs will incorrectly
  contain multiple bases.
  The base is appendedt to the WcmServletPath like
  http://localhost:10038/wps/wcm/myconnect where it should be
  wps/wcm/myconnect.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• WCM
  

Fix information

• Fixed component name

  LOTUS WEB CONT

• Fixed component ID

  5724I2900

Applicable component levels

• R60H PSY

     UP