Hi Ken,

no, i don't have a portlet or package to replicate the problem.

I use my whole "in place" portal, yet running perfecly with PBR 2.1.0 and 2.2.0.

I though of it, but it is difficult to extract the portlets and jsf views, as they come with all the coding around, amoung which the security things etc,...

************************

the context params in the web.xml :

there are several wars, with the same config in the web.xml.

they all have the same problem.

here are only the context param, because the other part are very similar to usual web.xml for jsf/richfaces, but with few details added for security.

 <context-param>
  <param-name>contextConfigLocation</param-name>
  <param-value>/WEB-INF/portlet.xml</param-value>
 </context-param>
 <context-param>
  <param-name>facelets.BUILD_BEFORE_RESTORE</param-name>
  <param-value>false</param-value>
 </context-param>
 <context-param>
  <param-name>facelets.DEVELOPMENT</param-name>
  <param-value>false</param-value>
 </context-param>
 <context-param>
  <param-name>facelets.RECREATE_VALUE_EXPRESSION_ON_BUILD_BEFORE_RESTORE</param-name>
  <param-value>false</param-value>
 </context-param>
 <context-param>
  <param-name>facelets.SKIP_COMMENTS</param-name>
  <param-value>true</param-value>
 </context-param>
 <context-param>
  <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
  <param-value>.xhtml</param-value>
 </context-param>
 <context-param>
  <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
  <param-value>server</param-value>
 </context-param>
 <context-param>
  <param-name>javax.portlet.faces.RENDER_POLICY</param-name>
  <param-value>ALWAYS_DELEGATE</param-value>
 </context-param>
 <context-param>
  <param-name>org.ajax4jsf.COMPRESS_SCRIPT</param-name>
  <param-value>false</param-value>
 </context-param>
 <context-param>
  <param-name>org.ajax4jsf.RESOURCE_URI_PREFIX</param-name>
  <param-value>rfRes</param-value>
 </context-param>
 <context-param>
  <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
  <param-value>org.jboss.portletbridge.application.FaceletPortletViewHandler</param-value>
 </context-param>
 <context-param>
  <param-name>org.ajax4jsf.handleViewExpiredOnClient</param-name>
  <param-value>true</param-value>
 </context-param>
 <context-param>
  <!-- See : JBoss Portlet Bridge Reference Guide : 
  Richfaces does not account for multiple components on the same portal page by default. 
  This following web.xml renders all RichFaces component javascript to be portal friendly.  -->
  <param-name>org.jboss.portletbridge.WRAP_SCRIPTS</param-name>
  <param-value>true</param-value>
 </context-param>
 <context-param>
  <param-name>org.richfaces.CONTROL_SKINNING</param-name>
  <param-value>enable</param-value>
 </context-param>
 <!-- 
 <context-param>
  <param-name>org.richfaces.CONTROL_SKINNING_CLASSES</param-name>
  <param-value>enable</param-value>
 </context-param>
 <context-param>
  <param-name>org.richfaces.CONTROL_SKINNING_LEVEL</param-name>
  <param-value>extended</param-value>
 </context-param> 
 -->
 <context-param>
  <param-name>org.richfaces.LoadScriptStrategy</param-name>
  <param-value>ALL</param-value>
 </context-param>
 <context-param>
  <param-name>org.richfaces.LoadStyleStrategy</param-name>
  <param-value>ALL</param-value>
 </context-param>
 <context-param>
  <param-name>org.richfaces.SKIN</param-name>
  <!-- <param-value>blueSky</param-value>
  <param-value>classic</param-value>
  <param-value>pexUsualRFSkin</param-value>
  -->
  <param-value>pexUsualRFSkin</param-value>
 </context-param>

yes the CONTROL_SKINNING is enable.

I don't use the CONTROL_SKINNING_CLASSES, nor the CONTROL_SKINNING_LEVEL.

They are there, commented, because I also made some trials with them... but it does not work anyway.

note : every thing was working fine for a year, and is still with PBR 2.2.0 FINAL.

**************************************************************

I am sorry I cannot dig for this problem more now. I have the portal to set for testing then prod (that's why I tried to update the bridge, just before going to test).

but, if I may : where this "rich-extended-skinning" character string comes from ?

it does not come from nowhere...

and alos : what part of the code is building and writting the "link" element, for the CSS ?

there should be the explaination why there is now a media="rich-extended-skinning" that was not there before.

for the Ajax not working in some portlet, I don't know how to search right know.

I'll try to make something to reproduce the problem, starting from my code that shows it.

thanks,

Antoine

JBoss Portal and GateIn (JSR-286), JSF, Richfaces, J2EE, Drools, BRMS.

http://www.presta-expert.com/

Hi,

Good news, with WRAP_SCRIPTS set to false, the problems vanishes...

I know the bug RF-11975, as I struggled with it last automn when building another portal.

For this portal today, I don't have two TogglePanel in the same page.

So, I can set the WRAP_SCRIPTS to false in all the wars, and everything still runs ok.

Note : I have at least 2 portlets with RichFaces on each page. One is the login window, on top right corner of the page, and the other is the body of the page.

Some pages have 2 portlets in the body, so it make 3 RichFaces portlets.

All seems to run ok, ... I guess it's because I don't use 2 toggle panel in a page.

***************

For :

If I understood the original description of your problem, with this simple portlet the input fields and button wouldn't be skinned the same as the panel (extended skinning), and the switching between different panels didn't work (ajax issue).  Please correct me if this isn't accurate.

yes.

the problems are :

- Skinning : the buttons, the input fields, and the panel header are not skinned (with extended skinning). They remain with a basic html rendering.

- Ajax : the buttons do not trigger the actions. The toggle panel do not switch. The calendars do not drop down the panel to chose the date. I cannot see any error happen in the scripts.

***************

Could you explain what's going on ?

And give some indication where in the code (classes, methods?) where the things are done (with and without the problem) ?

Feel free to ask, for testing and helping to solve this.

Thanks a lot for helping.

Antoine

JBoss Portal and GateIn (JSR-286), JSF, Richfaces, J2EE, Drools, BRMS.

http://www.sysemo.com

yes, both...

yes : "the problems vanish..." (without "es" at the end).