1 2 Previous Next 16 Replies Latest reply on Nov 12, 2007 11:00 AM by scryan7371

    Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandButto

    scryan7371
    scryan7371 Sep 19, 2007 6:18 PM

      I have an application that uses myfaces and facelets. I recently upgraded to a new version of richfaces 3.1.0 which brought along a new integrated ajax4jsf library.

      When I run my application my h:commandButtons no longer execute. I tried using immediate true and false with the same results.

      The buttons render however my page does not forward to the new page. I have mapped a to-view-id with a from-outcome entry in my faces config which work with the older version of ajax4jsf but not the new one. The page bean is in request scope.

      If I roll back to a previous version of ajax4jsf 1.0.6 everything works. So it looks like the version of ajax4jsf that is included in the new richfaces 3.1.0 is my issue. I also tried using a later version of ajax4jsf with the same results so any version of ajax4jsf after 1.0.6 breaks my commandButton objects. I am using the following:

      Myfaces 1.1.5
      facelets 1.1.11
      jetty
      firefox
      ajax4jsf 1.0.6 works with richfaces 3.0.1

      This happens for all pages even those not using either ajax4jsf or richfaces.


      If you need more information please let me know of if there are ways to debug this issue I would appreciate it.

      Thanks
      Scott Ryan

      • 10016 Views
      • Tags:
        • 1. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandB
          sergeysmirnov Sep 19, 2007 6:31 PM (in response to scryan7371)

          code snippet will be much appreciated.

            • Actions
          • 2. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my h:commandB
            scryan7371
            scryan7371 Sep 19, 2007 7:07 PM (in response to scryan7371)

            Here is the page but even pages without the a4j and rich includes dont work.

            <html xmlns="http://www.w3.org/1999/xhtml"
 xmlns:c="http://java.sun.com/jstl/core"
 xmlns:f="http://java.sun.com/jsf/core"
 xmlns:h="http://java.sun.com/jsf/html"
 xmlns:ui="http://java.sun.com/jsf/facelets"
 xmlns:t="http://myfaces.apache.org/tomahawk"
 xmlns:a4j="http://richfaces.org/a4j"
 xmlns:rich="http://richfaces.org/rich">
<f:loadBundle var="text" basename="#{locationController.bundleName}" />
<head>
<title>#{text['locationList.title']}</title>
<meta name="heading" content="#{text['locationList.heading']}" />
<meta name="menu" content="LocationMenu" />
</head>
<body id="locationList">
<h:form id="locationList">
 <h:commandButton value="#{text['button.add']}" action="add" id="add"
 immediate="false" styleClass="button" />
 <h:commandButton value="#{text['button.done']}" action="mainMenu"
 id="cancel" immediate="true" styleClass="button"
 style="margin-left: 5px" />
 <!-- Error from this table is caused by http://issues.apache.org/jira/browse/TOMAHAWK-466 -->
 <t:dataTable id="locations" var="location" style="margin-top: 10px"
 value="#{locationController.locations}" rows="25"
 sortColumn="#{locationController.sortColumn}"
 sortAscending="#{locationController.ascending}"
 styleClass="scrollerTable table data"
 headerClass="standardTable_Header"
 rowClasses="standardTable_Row1,standardTable_Row2"
 columnClasses="standardTable_Column,standardTable_Column,
 standardTable_Column,standardTable_Column,standardTable_ColumnCentered">
 <t:column>
 <f:facet name="header">
 <t:commandSortHeader columnName="id" arrow="true">
 <h:outputText value="#{text['location.locationId']}" />
 </t:commandSortHeader>
 </f:facet>
 <h:commandLink action="#{locationController.edit}"
 value="#{location.locationId}">
 <f:param name="id" value="#{location.id}" />
 <f:param name="from" value="list" />
 </h:commandLink>
 </t:column>
 <t:column>
 <f:facet name="header">
 <t:commandSortHeader columnName="locationName" arrow="true">
 <h:outputText value="#{text['location.locationName']}" />
 </t:commandSortHeader>
 </f:facet>
 <h:outputText value="#{location.locationName}" escape="true" />
 </t:column>
 <t:column>
 <f:facet name="header">
 <t:commandSortHeader columnName="address" arrow="true">
 <h:outputText value="#{text['location.address']}" />
 </t:commandSortHeader>
 </f:facet>
 <h:outputText value="#{location.address}" escape="true" />
 </t:column>
 <t:column>
 <f:facet name="header">
 <t:commandSortHeader columnName="city" arrow="true">
 <h:outputText value="#{text['location.city']}" />
 </t:commandSortHeader>
 </f:facet>
 <h:outputText value="#{location.city}" escape="true" />
 </t:column>
 <t:column>
 <f:facet name="header">
 <t:commandSortHeader columnName="province" arrow="true">
 <h:outputText value="#{text['location.province']}" />
 </t:commandSortHeader>
 </f:facet>
 <h:outputText value="#{location.province}" escape="true" />
 </t:column>
 <t:column>
 <f:facet name="header">
 <t:commandSortHeader columnName="primaryPhone" arrow="true">
 <h:outputText value="#{text['location.primaryPhone']}" />
 </t:commandSortHeader>
 </f:facet>
 <h:outputText value="#{location.primaryPhone}" escape="true" />
 </t:column>
 <t:column>
 <f:facet name="header">
 <t:commandSortHeader columnName="fax" arrow="true">
 <h:outputText value="#{text['location.fax']}" />
 </t:commandSortHeader>
 </f:facet>
 <h:outputText value="#{location.fax}" escape="true" />
 </t:column>
 </t:dataTable>
 <ui:include src="/common/tableFooter.xhtml">
 <ui:param name="tableName" value="locations" />
 </ui:include>
 <script type="text/javascript">
 highlightTableRows("locationList:locations");
</script>
</h:form>
</body>
</html>


              • Actions
            • 3. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandB
              sergeysmirnov Sep 19, 2007 7:17 PM (in response to scryan7371)

              Ok. It is not about the code, but about configuration.

              Could you drop couple words about "dont work". What are the symptoms ?

                • Actions
              • 4. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandB
                scryan7371
                scryan7371 Sep 19, 2007 7:26 PM (in response to scryan7371)

                THe page renders correctly. When I press either command button the page blinks but does not execute to the next step. when I have the 3.0.1 code and press the command button it goes on to the next page as expected and defined in the faces config as follows: I would expect that with immediate set to true on the add button it would move on to the locationDetail.html page as it does on 3.0.1. There is nothing on the logs and nothing to validate to I doubt conversions or validations are getting me.

                <!-- Locations Rule Begin -->
                <navigation-rule>
                <from-view-id>/locations.xhtml</from-view-id>
                <navigation-case>
                <from-outcome>add</from-outcome>
                <to-view-id>/locationDetail.xhtml</to-view-id>
                </navigation-case>
                <navigation-case>
                <from-outcome>edit</from-outcome>
                <to-view-id>/locationDetail.xhtml</to-view-id>
                </navigation-case>
                </navigation-rule>
                <navigation-rule>
                <from-view-id>/locationDetail.xhtml</from-view-id>
                <navigation-case>
                <from-outcome>cancel</from-outcome>
                <to-view-id>/locations.xhtml</to-view-id>

                </navigation-case>
                <navigation-case>
                <from-outcome>list</from-outcome>
                <to-view-id>/locations.xhtml</to-view-id>

                </navigation-case>
                </navigation-rule>
                <!-- Location Rules End -->

                  • Actions
                • 5. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandB
                  sergeysmirnov Sep 19, 2007 8:13 PM (in response to scryan7371)

                  Still hard to recognize any relation between the behavior and the RichFaces/Ajax4jsf as soon as you did not use them on the page.

                  Do you have some small test application that demonstrate the problem?


                  If you click the link, but page just refreshed, this point to the fact that your application does not pass the 5th phase of the lifecycle.

                  Download and install the JSF phasetracker and see when phases are passed when you click the button.

                  http://www.jsftutorials.net/faces-config/phaseTracker.html

                    • Actions
                  • 6. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandB
                    scryan7371
                    scryan7371 Sep 19, 2007 8:31 PM (in response to scryan7371)

                    It looks like it is skipping most of the phases when it is not working. I imagine this is some setting in ajax4jsf that might be new? I don't have a small application but can build one in the next few days. This project is an open source project on Sourceforge so I could push up the code there and you could svn it and I could walk you through the changes.

                    Phase Tracker when it works:

                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE RESTORE_VIEW(1)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE RESTORE_VIEW(1)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER RESTORE_VIEW(1)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER RESTORE_VIEW(1)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE APPLY_REQUEST_VALUES(2)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE APPLY_REQUEST_VALUES(2)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER APPLY_REQUEST_VALUES(2)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER APPLY_REQUEST_VALUES(2)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE PROCESS_VALIDATIONS(3)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE PROCESS_VALIDATIONS(3)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER PROCESS_VALIDATIONS(3)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER PROCESS_VALIDATIONS(3)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE UPDATE_MODEL_VALUES(4)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE UPDATE_MODEL_VALUES(4)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER UPDATE_MODEL_VALUES(4)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER UPDATE_MODEL_VALUES(4)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE INVOKE_APPLICATION(5)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE INVOKE_APPLICATION(5)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER INVOKE_APPLICATION(5)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER INVOKE_APPLICATION(5)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE RENDER_RESPONSE(6)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE RENDER_RESPONSE(6)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER RENDER_RESPONSE(6)
                    Sep 19, 2007 6:28:41 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER RENDER_RESPONSE(6)



                    Phase Tracker when it does not work:

                    Sep 19, 2007 6:25:57 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE RESTORE_VIEW(1)
                    Sep 19, 2007 6:25:57 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE RESTORE_VIEW(1)
                    Sep 19, 2007 6:25:57 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER RESTORE_VIEW(1)
                    Sep 19, 2007 6:25:57 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER RESTORE_VIEW(1)
                    Sep 19, 2007 6:25:57 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE RENDER_RESPONSE(6)
                    Sep 19, 2007 6:25:57 PM org.exadel.jsf.PhaseTracker beforePhase
                    INFO: BEFORE RENDER_RESPONSE(6)
                    Sep 19, 2007 6:25:57 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER RENDER_RESPONSE(6)
                    Sep 19, 2007 6:25:57 PM org.exadel.jsf.PhaseTracker afterPhase
                    INFO: AFTER RENDER_RESPONSE(6)

                      • Actions
                    • 7. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandB
                      scryan7371
                      scryan7371 Sep 19, 2007 8:34 PM (in response to scryan7371)

                      Here is the phase tracker with immediate set to true: It looks like when i run successfully I get a phase (2) so what would keep me from getting a phase 2 with the new jar?

                      Working:

                      Sep 19, 2007 6:32:03 PM org.exadel.jsf.PhaseTracker beforePhase
                      INFO: BEFORE RESTORE_VIEW(1)
                      Sep 19, 2007 6:32:03 PM org.exadel.jsf.PhaseTracker beforePhase
                      INFO: BEFORE RESTORE_VIEW(1)
                      Sep 19, 2007 6:32:03 PM org.exadel.jsf.PhaseTracker afterPhase
                      INFO: AFTER RESTORE_VIEW(1)
                      Sep 19, 2007 6:32:03 PM org.exadel.jsf.PhaseTracker afterPhase
                      INFO: AFTER RESTORE_VIEW(1)
                      Sep 19, 2007 6:32:03 PM org.exadel.jsf.PhaseTracker beforePhase
                      INFO: BEFORE APPLY_REQUEST_VALUES(2)
                      Sep 19, 2007 6:32:03 PM org.exadel.jsf.PhaseTracker beforePhase
                      INFO: BEFORE APPLY_REQUEST_VALUES(2)
                      Sep 19, 2007 6:32:03 PM org.exadel.jsf.PhaseTracker afterPhase
                      INFO: AFTER APPLY_REQUEST_VALUES(2)
                      Sep 19, 2007 6:32:03 PM org.exadel.jsf.PhaseTracker afterPhase
                      INFO: AFTER APPLY_REQUEST_VALUES(2)
                      Sep 19, 2007 6:32:03 PM org.exadel.jsf.PhaseTracker beforePhase
                      INFO: BEFORE RENDER_RESPONSE(6)
                      Sep 19, 2007 6:32:03 PM org.exadel.jsf.PhaseTracker beforePhase
                      INFO: BEFORE RENDER_RESPONSE(6)
                      Sep 19, 2007 6:32:03 PM org.exadel.jsf.PhaseTracker afterPhase
                      INFO: AFTER RENDER_RESPONSE(6)
                      Sep 19, 2007 6:32:03 PM org.exadel.jsf.PhaseTracker afterPhase
                      INFO: AFTER RENDER_RESPONSE(6)


                      Not Working:


                      Sep 19, 2007 6:33:55 PM org.exadel.jsf.PhaseTracker beforePhase
                      INFO: BEFORE RESTORE_VIEW(1)
                      Sep 19, 2007 6:33:55 PM org.exadel.jsf.PhaseTracker beforePhase
                      INFO: BEFORE RESTORE_VIEW(1)
                      Sep 19, 2007 6:33:55 PM org.exadel.jsf.PhaseTracker afterPhase
                      INFO: AFTER RESTORE_VIEW(1)
                      Sep 19, 2007 6:33:55 PM org.exadel.jsf.PhaseTracker afterPhase
                      INFO: AFTER RESTORE_VIEW(1)
                      Sep 19, 2007 6:33:55 PM org.exadel.jsf.PhaseTracker beforePhase
                      INFO: BEFORE RENDER_RESPONSE(6)
                      Sep 19, 2007 6:33:55 PM org.exadel.jsf.PhaseTracker beforePhase
                      INFO: BEFORE RENDER_RESPONSE(6)
                      Sep 19, 2007 6:33:55 PM org.exadel.jsf.PhaseTracker afterPhase
                      INFO: AFTER RENDER_RESPONSE(6)
                      Sep 19, 2007 6:33:55 PM org.exadel.jsf.PhaseTracker afterPhase
                      INFO: AFTER RENDER_RESPONSE(6)

                        • Actions
                      • 8. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandB
                        sergeysmirnov Sep 19, 2007 9:05 PM (in response to scryan7371)

                        Jumping from 1sf phase to 6th means that JSF implementation cannot find ant/or restore the component tree, create the brand new one and continue with rendering. Non-JSF request, session expiration, loosing saved state (if client-side saving method) are the major reasons.
                        I have no idea how you get this situation. The source of the problem still outside of what you posted. let's continue with test project.

                          • Actions
                        • 9. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandB
                          sergeysmirnov Sep 19, 2007 9:09 PM (in response to scryan7371)

                          BWT, printing the log message twice for each point in not so good. Could you post your web.xml snippet (where JSF stuff is mentioned)

                            • Actions
                          • 10. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandB
                            scryan7371
                            scryan7371 Sep 19, 2007 10:30 PM (in response to scryan7371)

                            Web.xml is here

                            <?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
 <display-name>appfuse</display-name>
 <distributable />
 <!-- precompiled jsp mappings -->
 <!-- Define the default CSS Theme -->
 <context-param>
 <param-name>csstheme</param-name>
 <param-value>simplicity</param-value>
 </context-param>
 <!-- Define the basename for a resource bundle for I18N -->
 <context-param>
 <param-name>
 javax.servlet.jsp.jstl.fmt.localizationContext
 </param-name>
 <param-value>ApplicationResources</param-value>
 </context-param>
 <!-- Fallback locale if no bundles found for browser's preferred locale -->
 <!-- Force a single locale using param-name 'javax.servlet.jsp.jstl.fmt.locale' -->
 <context-param>
 <param-name>javax.servlet.jsp.jstl.fmt.fallbackLocale</param-name>
 <param-value>en</param-value>
 </context-param>
 <!-- Context Configuration locations for Spring XML files -->
 <context-param>
 <param-name>contextConfigLocation</param-name>
 <param-value>
 classpath*:/applicationContext-resources.xml
 classpath*:/applicationContext-dao.xml
 classpath*:/applicationContext-service.xml
 classpath*:/applicationContext.xml
 /WEB-INF/applicationContext*.xml /WEB-INF/xfire-servlet.xml
 /WEB-INF/security.xml
 </param-value>
 </context-param>
 <context-param>
 <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
 <param-value>com.sun.facelets.FaceletViewHandler</param-value>
 </context-param>
 <context-param>
 <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
 <param-value>client</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>facelets.DEVELOPMENT</param-name>
 <param-value>true</param-value>
 </context-param>
 <context-param>
 <param-name>facelets.LIBRARIES</param-name>
 <param-value>
 /WEB-INF/taglibs/corejsf-validator.taglib.xml;
 /WEB-INF/taglibs/tomahawk.taglib.xml;
 /WEB-INF/facelets/tags/appfuse.taglib.xml
 </param-value>
 </context-param>
 <filter>
 <filter-name>ajax4jsf</filter-name>
 <filter-class>org.ajax4jsf.Filter</filter-class>
 </filter>
 <filter>
 <filter-name>cacheFilter</filter-name>
 <filter-class>
 com.opensymphony.oscache.web.filter.CacheFilter
 </filter-class>
 </filter>
 <filter>
 <filter-name>clickstreamFilter</filter-name>
 <filter-class>
 com.opensymphony.clickstream.ClickstreamFilter
 </filter-class>
 </filter>
 <filter>
 <filter-name>encodingFilter</filter-name>
 <filter-class>
 org.springframework.web.filter.CharacterEncodingFilter
 </filter-class>
 <init-param>
 <param-name>encoding</param-name>
 <param-value>UTF-8</param-value>
 </init-param>
 <init-param>
 <param-name>forceEncoding</param-name>
 <param-value>true</param-value>
 </init-param>
 </filter>
 <filter>
 <filter-name>extensionsFilter</filter-name>
 <filter-class>
 org.apache.myfaces.webapp.filter.ExtensionsFilter
 </filter-class>
 <init-param>
 <param-name>maxFileSize</param-name>
 <param-value>2m</param-value>
 </init-param>
 </filter>
 <filter>
 <filter-name>gzipFilter</filter-name>
 <filter-class>
 net.sf.ehcache.constructs.web.filter.GzipFilter
 </filter-class>
 </filter>
 <!--<filter>
 <filter-name>lazyLoadingFilter</filter-name>
 <filter-class>org.springframework.orm.hibernate3.support.OpenSessionInViewFilter</filter-class>
 </filter>-->
 <!-- Use "org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter" if you're using JPA -->
 <filter>
 <filter-name>localeFilter</filter-name>
 <filter-class>
 com.soaringeagleco.swoop.webapp.filter.LocaleFilter
 </filter-class>
 </filter>
 <filter>
 <filter-name>messageFilter</filter-name>
 <filter-class>
 com.soaringeagleco.swoop.webapp.filter.MessageFilter
 </filter-class>
 </filter>
 <filter>
 <filter-name>rewriteFilter</filter-name>
 <filter-class>
 org.tuckey.web.filters.urlrewrite.UrlRewriteFilter
 </filter-class>
 <init-param>
 <param-name>logLevel</param-name>
 <param-value>log4j</param-value>
 </init-param>
 </filter>
 <filter>
 <filter-name>securityFilter</filter-name>
 <filter-class>
 org.acegisecurity.util.FilterToBeanProxy
 </filter-class>
 <init-param>
 <param-name>targetClass</param-name>
 <param-value>org.acegisecurity.util.FilterChainProxy</param-value>
 </init-param>
 </filter>
 <filter>
 <filter-name>sitemesh</filter-name>
 <filter-class>
 com.opensymphony.module.sitemesh.filter.PageFilter
 </filter-class>
 </filter>
 <filter-mapping>
 <filter-name>ajax4jsf</filter-name>
 <servlet-name>faces</servlet-name>
 <dispatcher>REQUEST</dispatcher>
 <dispatcher>FORWARD</dispatcher>
 <dispatcher>INCLUDE</dispatcher>
 </filter-mapping>
 <filter-mapping>
 <filter-name>encodingFilter</filter-name>
 <url-pattern>/*</url-pattern>
 </filter-mapping>
 <filter-mapping>
 <filter-name>securityFilter</filter-name>
 <url-pattern>/*</url-pattern>
 </filter-mapping>
 <filter-mapping>
 <filter-name>extensionsFilter</filter-name>
 <servlet-name>faces</servlet-name>
 </filter-mapping>
 <filter-mapping>
 <filter-name>extensionsFilter</filter-name>
 <url-pattern>/faces/myFacesExtensionResource/*</url-pattern>
 </filter-mapping>
 <!-- Commented out for 2 reasons: 1) it's a pain when developing JSPs, and
 2) it causes the Signup webtest to fail -->
 <!--filter-mapping>
 <filter-name>cacheFilter</filter-name>
 <url-pattern>*.jsp</url-pattern>
 </filter-mapping-->
 <!--<filter-mapping>
 <filter-name>lazyLoadingFilter</filter-name>
 <url-pattern>/*</url-pattern>
 </filter-mapping>-->
 <filter-mapping>
 <filter-name>clickstreamFilter</filter-name>
 <url-pattern>/*</url-pattern>
 </filter-mapping>
 <filter-mapping>
 <filter-name>localeFilter</filter-name>
 <url-pattern>/*</url-pattern>
 </filter-mapping>
 <filter-mapping>
 <filter-name>gzipFilter</filter-name>
 <url-pattern>/*</url-pattern>
 </filter-mapping>
 <filter-mapping>
 <filter-name>rewriteFilter</filter-name>
 <url-pattern>/*</url-pattern>
 <dispatcher>REQUEST</dispatcher>
 <dispatcher>FORWARD</dispatcher>
 </filter-mapping>
 <filter-mapping>
 <filter-name>sitemesh</filter-name>
 <url-pattern>/*</url-pattern>
 <dispatcher>REQUEST</dispatcher>
 <dispatcher>FORWARD</dispatcher>
 </filter-mapping>
 <filter-mapping>
 <filter-name>messageFilter</filter-name>
 <url-pattern>*.html</url-pattern>
 <dispatcher>REQUEST</dispatcher>
 <dispatcher>FORWARD</dispatcher>
 </filter-mapping>
 <listener>
 <listener-class>
 com.opensymphony.clickstream.ClickstreamListener
 </listener-class>
 </listener>
 <listener>
 <listener-class>
 org.apache.myfaces.webapp.StartupServletContextListener
 </listener-class>
 </listener>
 <listener>
 <listener-class>
 org.springframework.web.context.ContextLoaderListener
 </listener-class>
 </listener>
 <listener>
 <listener-class>
 org.springframework.web.util.IntrospectorCleanupListener
 </listener-class>
 </listener>
 <listener>
 <listener-class>
 org.springframework.web.context.request.RequestContextListener
 </listener-class>
 </listener>
 <listener>
 <listener-class>
 com.soaringeagleco.swoop.webapp.listener.StartupListener
 </listener-class>
 </listener>
 <listener>
 <listener-class>
 com.soaringeagleco.swoop.webapp.listener.UserCounterListener
 </listener-class>
 </listener>
 <listener>
 <listener-class>
 net.sf.navigator.menu.MenuContextListener
 </listener-class>
 </listener>
 <servlet>
 <servlet-name>faces</servlet-name>
 <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
 <load-on-startup>2</load-on-startup>
 </servlet>
 <servlet>
 <servlet-name>dwr-invoker</servlet-name>
 <servlet-class>
 org.directwebremoting.servlet.DwrServlet
 </servlet-class>
 <init-param>
 <param-name>debug</param-name>
 <param-value>true</param-value>
 </init-param>
 </servlet>
 <servlet>
 <servlet-name>xfire</servlet-name>
 <servlet-class>
 org.codehaus.xfire.spring.XFireSpringServlet
 </servlet-class>
 </servlet>
 <servlet>
 <servlet-name>notification</servlet-name>
 <servlet-class>
 com.soaringeagleco.swoop.servlet.NotificationServlet
 </servlet-class>
 <load-on-startup>1</load-on-startup>
 </servlet>
 <servlet-mapping>
 <servlet-name>faces</servlet-name>
 <url-pattern>*.html</url-pattern>
 </servlet-mapping>
 <servlet-mapping>
 <servlet-name>dwr-invoker</servlet-name>
 <url-pattern>/dwr/*</url-pattern>
 </servlet-mapping>
 <servlet-mapping>
 <servlet-name>xfire</servlet-name>
 <url-pattern>/services/*</url-pattern>
 </servlet-mapping>
 <session-config>
 <session-timeout>10</session-timeout>
 </session-config>
 <security-constraint>
 <web-resource-collection>
 <web-resource-name>Protect XHTML Templates</web-resource-name>
 <url-pattern>*.xhtml</url-pattern>
 </web-resource-collection>
 <auth-constraint />
 </security-constraint>
 <welcome-file-list>
 <welcome-file>index.jsp</welcome-file>
 </welcome-file-list>
 <error-page>
 <error-code>500</error-code>
 <location>/error.jsp</location>
 </error-page>
 <error-page>
 <error-code>400</error-code>
 <location>/index.jsp</location>
 </error-page>
 <error-page>
 <error-code>403</error-code>
 <location>/403.jsp</location>
 </error-page>
 <error-page>
 <error-code>404</error-code>
 <location>/404.jsp</location>
 </error-page>
</web-app>


                              • Actions
                            • 11. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandB
                              _jmax_
                              _jmax_ Sep 20, 2007 3:18 AM (in response to scryan7371)

                              Hi scryan7371,

                              Me too, I have a problem with 3.1.0 version.
                              I have a problem with a t:commandButton facelets composition.

                              A bug is open : http://jira.jboss.com/jira/browse/RF-653 , but its resolution is rejected.

                              I hope it will be fixed as soon as possible !

                                • Actions
                              • 12. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandB
                                ilya_shaikovsky
                                ilya_shaikovsky Sep 20, 2007 9:54 AM (in response to scryan7371)

                                are you sure that you do not use ajax4jsf.jar in classpath after update to 3.1.0?

                                And in case of 3.0.1 RF - it should works with ajax4jsf 1.1.1

                                  • Actions
                                • 13. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandB
                                  sergeysmirnov Sep 20, 2007 2:10 PM (in response to scryan7371)

                                  scryan7371, could you confirm that you have no Ajax4jsf jar when you use RichFaces 3.1.0 jars?

                                    • Actions
                                  • 14. Re: Upgrading from 3.0.1 to 3.1.0 broke caused my j:commandB
                                    ghazouli
                                    ghazouli Sep 21, 2007 10:29 PM (in response to scryan7371)

                                    I too have run into the same problem. I removed the ajax4jsf and richfaces 3.0.1 and the submit broke. I have a to fix a couple of duplicate ids that 3.1 complained about. My page is a tab panel with server side switching. It works fine in 3.0.1 but once I plugged in 3.1 it stopped working.

                                      • Actions
                                    1 2 Previous Next