My Oracle Support Banner

AJAX Limitations In Federated Portal Environment (Doc ID 1268789.1)

Last updated on JULY 13, 2020

Applies to:

Oracle WebLogic Portal - Version 10.3.0 and later
Information in this document applies to any platform.


Some of the features of AJAX (Asynchronous JavaScript and XML) such as autocomplete functionality of textbox may not work in a remote Portlet of WebLogic Portal. It works fine when accessing it directly from the Web Services for Remote Portlets (WSRP) Producer Portlet but fails while accessing through Consumer Portlet.
Please find some sample code below:

  1. Build the URL by using render tag in JSP:
    <render:resourceUrl contextualpath="/testAjaxController/" var="dataUrl"/>
  2. Sample JavaScript to call page flow action using Portal Aware XMLHttpRequest as follows:
function testAjax() {
   var inputId = lookupIdByTagId("inputBox",this);
   var input = document.getElementById(inputId).value;
   var dataUrl1="${dataUrl}";
   dataUrl1 = dataUrl1 + "&input="+input;
   alert("the text is:"+dataUrl1);
   var xmlhttp = new;
   xmlhttp.onreadystatechange = function()
     //alert("in on readystate"+xmlhttp.readyState +" and status is"+xmlhttp.status);
     if ((xmlhttp.readyState == 4) && (xmlhttp.status == 200))
        alert("response text is = "+xmlhttp.responseText);
        var formTagId = lookupIdByTagId("resultBox",this);
   }'GET', dataUrl1, true);


NOTE: The code above represent a fictitious sample.  Any similarity to actual environments, past or present, or users, living or dead, is purely coincidental and not intended in any manner.




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

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