JSP Portlet with StandalonePortletUrl Tag Not Supported as a Proxy Portlet (Doc ID 1316160.1)

Last updated on MARCH 07, 2025

Applies to:

Symptoms

Tag standalonePortletUrl does not work in a WSRP proxy portlet.
Let's assume you are using StandalonePortletURL class or render:standalonePortletUri tag in a producer portal to include a portlet in another portlet using iframe.
When running the producer portal directly it works fine, but calling the producer using the consumer portal via WSRP, the portlet displayed as a standalone portlet is the wrong one, it seems that this functionality doesn't work using WSRP.

Steps to reproduce:
1. Create 2 portal applications (web + ear), one consumer, one producer (deployed on same server).
2. In the producer web project, create 2 jsp portlets portlet1.jsp and portlet2.jsp The first includes the following code:

3. Add portlet1 on a desktop, and display the desktop: we can see the standalone portlet2 in an iframe.
4. In the consumer, add the WSRP producer from the producer web app, and add portlet1 to a desktop:The behavior is different: in the iframe, we can see portlet1 and not portlet2

Changes

Cause

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