-
1. Re: aj4 calls failing in jboss portal 2.7.2
wesleyhales Sep 4, 2009 9:39 AM (in response to lakshmi.rath)Upgrade to the latest CR2 bridge and try again.
-
2. Re: aj4 calls failing in jboss portal 2.7.2
lakshmi.rath Sep 4, 2009 2:44 PM (in response to lakshmi.rath)Hi Wesley,
Thanks for the prompt response.
I will surely try out CR2 and check.
Meanwhile, we also gave a try with PortletBridge2.0Alpha and found a4j calls happening properly in SSL. Hence wanted to check if it is ok to use Alpha version in production.
Also, is Beta/Stable release expected soon.
Thank you for all your support.
regards,,
Lakshmi -
3. Re: aj4 calls failing in jboss portal 2.7.2
animasgsw Oct 5, 2009 4:03 AM (in response to lakshmi.rath)Hi ,
We tried with following versions and see Ajax calls are happening -
richfaces(3.3.0 GA)
jsf-facelets-1.1.15.B1.jar
JBossPortletBridge-1.0.0.CR1
Configuration done for this is as below -
<context-param><param-name>com.sun.faces.enableRestoreView11Compatibility</param-name>
<param-value>true</param-value></context-param>
However we see following changes in behaviour -
1.JSF beans which are stored in session can't be fetched from JSF SessionMap (probably as this uses HTTPSession and not PortalSession)
Hence the standard call
appSecBeanInst = (ApplicationSecurityDataBean) context
.getExternalContext().getSessionMap().get(ApplicationConstants.APPLICATIONSECDATABEAN)
is not working as expected(SessionMap is coming as empty object)
2.Unlike FaceletViewHandler , the PortletViewHandler(used as View handler) prefixes Portalname,Pagename and Window name with every JSF element id . Hence any JavaScript calls which are made using document.getElementByid.. are failing.
Please guide us how to address this issues, as those are being used in our application earlier.