My Oracle Support Banner

JSP SSXA Tag Libraries Issue Within Portlets (Doc ID 1505227.1)

Last updated on SEPTEMBER 10, 2019

Applies to:

Oracle WebCenter Content - Version 11.1.1.4.0 and later
Information in this document applies to any platform.

Goal

Using SSXA tags in java/jsp portlets causes the contributor javascript files to be loaded multiple times based on each instance of the contributor portlet. The issue happens only when there is more than one contribution portlet on the page. In this case the DHTML tag to allow contribution is not shown.
The following javascript file has been specifically found to be responsible for the issue:
.../wcm/idc/resources/wcm/sitestudio/wcm.contributor.js
In this case the wcm.contributor.js file is loaded many times by the browser. Many async JS events are launched and caught by wcm.contributor.js itself so Site Studio DHTML tag are depicted and removed many times generating the issue.
Consulting has come up with a workaround.

This Workaround seems to work properly in every situation and use cases tested so far.

The client needs the following from Oracle:
1. An analysis if the situation where the JSP OOTB SSXA tags wcm:staticPlaceholder and wcm:placeholder are contained within portlets would result in the above issue.
2. If the above is true, can a SSXA product bug be logged?
3. Can the workaround be validated as possible solution of the above bug?
4. Is there any special OOTB flag to be set on SSXA layer so that in case of portal context the SSXA OOTB JSs are not re-sourced in the HTML code for every wcm placeholder tag inserted in the page causing the issue.
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.