h:form and h:commandButton tags are not functioning correctly in portlet environment ------------------------------------------------------------------------------------ Key: RF-2180 URL: http://jira.jboss.com/jira/browse/RF-2180 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.4 Reporter: Dirk Pitt Hallo, I had converted my demo application for richfaces and porlet running for JBoss Portal 2.6.3 with RichFaces 3.1.3.GA according these intructions (http://jira.jboss.com/jira/browse/RF-1271 end of the page) and directly hit some problems that I consider as bugs. First my application that is running with 3.1.3.GA using h:form and h:commandButton (in the forms that I don't need Ajax functionality) without problem, after the conversion to 3.1.4.GA with above configuration it stoped working. First problem, if I don't convert h:commanButton to a a4j:commandButton I am getting view expired exception all the time form JSF lifecycle. After this conversion, view expired exception dissappears but new javascript exception appears, complaining A4J object can't be found in Internet Explorer, including a4j:form solve this problem also. So at this point the question that I will ask, to use the Porlet and RichFaces, we have to stick to the a4j:form and a4j:commandButton, which I found weird because my previous version of application run perfectly with tags h:form and h:commandButton and actually I like to have the option to stick with standars JSF lifecycle when I don't need Ajax functionality.... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira