Note that there are some explanatory texts on larger screens.

plurals
  1. POWebsphere portal, jboss portlet bridge, jsf, richfaces, facelets - HTTP 500 OK message - issue with a4j modal panel, rich tooltip
    text
    copied!<p>We are using the following: Websphere Portal 6.1.0.2 Websphere App Server 7.0.0.17 Richfaces - 3.3.3 facelets - jsf-facelets-1.1.15 tomahawk12 - 1.1.9 Jboss portlet bridge - 2.1 final</p> <p>This configuration is mostly working fine on our portal environment and completely works when accessed through app/portal server directly. </p> <p>When accessed through the IHS web server, all the page comes up but when looked through firebug/httpfox, etc see HTTP 500 OK messages on richfaces and a4j related resources like org.ajax4jsf.javascript.AjaxScript and org.ajax4jsf.javascript.PrototypeScript, org/richfaces/renderkit/html/scripts/jquery/jquery.js and org/richfaces/renderkit/html/scripts/tooltip.js</p> <p>If I look at the content for those files, it has every bit of data, but just a stamp of 500 OK for the GET request for those resources and the browser is ignoring using those resources. I have tried firefox, IE 7/8, chrome and the modal panel and tooltip does not work and in IE it complaing AFJ undefined, tooltip undefined, etc. I have scoured throuh forums and have tried a lot of suggestions and have not been lucky. Have also tried making the resources available directly, but have not been lucky with that as well. </p> <p>Like I said earlier, it works just fine when accessing it through Websphere portal server directly. All the components work just fine.</p> <p>So, wanted to check with knowledgable people on stack overflow if they can shed any light on why I get errors about A4J, Tooltip, ModalPanel undefined when accessing through a web server (eventhough the resources needed looks like is being sent correctly except its been stamped with a 500 OK error message). I can provide any additional details necessary.</p> <p>Appreciate any help in getting this mystery solved.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload