javax.servlet.ServletException: org.ajax4jsf.application.AjaxStateHolder incompatible with org.ajax4jsf.application.StateHolder
Hi folks, i have a issue, im working with richfaces 3.3 and i have 2 projects, when im log in to 1 application this works fine, but when i tried to check another application then i get the next error:
Error 500: javax.servlet.ServletException: org.ajax4jsf.application.AjaxStateHolder incompatible with org.ajax4jsf.application.StateHolder
I gonna put and attach the 2 faces-config y web.xml
Thanks for eveything.
Project 1:
<lifecycle> <phase-listener>com.ibm.faces.webapp.ValueResourcePhaseListener</phase-listener> </lifecycle> <lifecycle> <phase-listener>mx.com.profuturo.mit.controlPolizas.integracion.presentacion.util.LifeCycleListener</phase-listener> </lifecycle> <!-- variable/property resolver registration --> <application> <variable-resolver>com.ibm.faces.databind.SelectItemsVarResolver</variable-resolver> <state-manager>com.ibm.faces.application.DevelopmentStateManager</state-manager> <property-resolver>com.ibm.faces.databind.SelectItemsPropResolver</property-resolver> <variable-resolver>org.springframework.web.jsf.DelegatingVariableResolver</variable-resolver> <locale-config><default-locale>es_MX</default-locale></locale-config> </application> <application> <!-- <message-bundle>WEB-INF.conf.mensajes.mensajesPresentacion</message-bundle>--> <message-bundle>mx.com.profuturo.mit.infraestructura.properties.mensajesPresentacion</message-bundle> </application>
<!--Inicia configuracion del context de JSF.--> <context-param> <description> Monitors Faces JSP files for modifications and synchronizes a running server with the changes without restarting the server. If this parameter is set to false or removed from the deployment descriptor, any changes made to Faces JSP files may not be seen by the server until it is restarted. This parameter is usually set to true while the Faces JSP files are being developed and debugged in order to improve the performance of the development environment. </description> <param-name>com.ibm.ws.jsf.JSP_UPDATE_CHECK</param-name> <param-value>true</param-value> </context-param> <context-param> <description> </description> <param-name>com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP</param-name> <param-value>true</param-value> </context-param> <!--Termina configuracion del context de JSF--> <context-param> <description> If set to true disables use of MultipartFacesContext, allowing underlying implementations to be used. MultipartFacesContext is required when the FileUpload component is used, and can be disabled otherwise. </description> <param-name>com.ibm.faces.DISABLE_JWL_MULTIPART_CONTEXT</param-name> <param-value>false</param-value> </context-param> <context-param> <description> Value, in milliseconds, to be used for Expires header for resources served by the JavaScript Resource Servlet. Default is never (31536000000 milliseconds or 1 year). </description> <param-name>com.ibm.faces.RESOURCE_EXPIRE_MS</param-name> <param-value>31536000000</param-value> </context-param> <context-param> <description> Defines the strictness of the conversion when converting from a string to a date. The higher the value, the more exactly the value must conform to the format. If 0 (liberal), all 'literals' are ignored while parsing a value, mis-ordered components will be rearranged, any missing component is supplied using the current datetime, misspellings and incomplete spellings are allowed (to the extent that they can be evaluated), 'E' and other non-unique components are ignored. If 1 (strict), all 'literals' are ignored while parsing a value, any missing component is supplied using the current datetime, misspellings and incomplete spellings are allowed (to the extent that they can be evaluated), 'E' and other non-unique components are ignored. For example if the pattern is MMMM dd, yyyy a user can enter 'Feb/02/04' and it will be parsed as February 02, 2004. If 2 (very strict), an exact match is required except long month names can be 'shortened' to the minimum number of unique characters and 'E' and other non-unique components are ignored. Literals must match exactly. Default is 1. </description> <param-name>com.ibm.faces.DATETIME_ASSIST_STRICTNESS</param-name> <param-value>1</param-value> </context-param> <context-param> <description> Defines the strictness of the conversion when converting from a string to a number. The higher the value, the more exactly the value must conform to the pattern. For numbers, currently strictness levels of 0 and 1 are equivalent. If the strictness is 2, if number is signed, the sign must be provided (otherwise it's assumed positive). Default is 1. </description> <param-name>com.ibm.faces.NUMBER_ASSIST_STRICTNESS</param-name> <param-value>1</param-value> </context-param> <context-param> <description> Defines the path for resources such as JavaScript libraries and images. The value can be either: 1. An empty string. Context path of the current application will be used. 2. A path string. Example: /project13. A number. Specifies the number of nodes to use from the context path starting from the left. Example: With a value of 1 if the context path is /screen/faces/SSID110267549/RID1102676 the path will be evaluated as /screen Default is an empty string. </description> <param-name>com.ibm.faces.USE_UNENCODED_CONTEXT_PATH</param-name> <param-value></param-value> </context-param> <context-param> <description> Sets a custom url-pattern for the JavaScript Resource servlet. Should match servlet mapping setting for the JavaScript Resource servlet. If the default default mapping value '/.ibmjsfres/*' is modified, this context-param should also be modified. </description> <param-name>com.ibm.faces.JS_RESOURCE_SERVLET_URL_PATTERN</param-name> <param-value>/.ibmjsfres/*</param-value> </context-param> <context-param> <description> If set to true, forces JavaScript Resource Servlet to cache all resources on the server. This can be useful when client-side caching is turned off. </description> <param-name>com.ibm.faces.JS_RESOURCE_SERVLET_CACHE</param-name> <param-value>false</param-value> </context-param> <context-param> <description> Sets a custom charset mapping properties file similar to converter.properties in WAS.</description> <param-name>com.ibm.faces.ENCODING_MAPPING</param-name> <param-value>converter.properties</param-value> </context-param> <context-param> <description> Number of Views to be stored in the session when Enhanced State Saving is being used. Default is 15. </description> <param-name>com.ibm.faces.ENHANCED_SERVER_STATE_SAVING_SESSION_STORED_VIEWS</param-name> <param-value>15</param-value> </context-param> <context-param> <description> If set to true, the entire JavaScript library, containing code for all components, will be included in the generated pages as one file. If set to false or removed, multiple smaller JavaScript files will be included, depending on the components used on the page.Default is false. </description> <param-name>com.ibm.faces.USE_HXCLIENT_FULL</param-name> <param-value>false</param-value> </context-param> <context-param> <description> Number of Views to be stored in the session when Server-Side State Saving is being used. Default is 15. </description> <param-name>com.sun.faces.numberOfViewsInSession</param-name> <param-value>15</param-value> </context-param> <context-param> <description> If set to true while server-side state saving is being used, a serialized representation of the view is stored on the server. This allows for failover and sever clustering support. Default is false. This parameter is not available in JSF 1.0. </description> <param-name>com.sun.faces.enableHighAvailability</param-name> <param-value>false</param-value> </context-param> <context-param> <description> If set to true while client-side state saving is being used, reduces the number of bytes sent to the client by compressing the state before it is encoded and written as a hidden field. Default is false. This parameter is not available in JSF 1.0.</description> <param-name>com.sun.faces.compressViewState</param-name> <param-value>false</param-value> </context-param> <context-param> <description> The location where state information is saved. Valid values are 'server' (typically saved in HttpSession) and 'client' (typically saved as a hidden field in the form. Default is server. </description> <param-name>javax.faces.STATE_SAVING_METHOD</param-name> <param-value>server</param-value> </context-param> <context-param> <description> Comma-delimited list of context-relative resource paths under which the JSF implementation will look for application configuration resources, before loading a configuration resource named /WEB-INF/facesconfig.xml (if such a resource exists). </description> <param-name>javax.faces.CONFIG_FILES</param-name> <param-value></param-value> </context-param> <context-param> <description> The default suffix for extension-mapped resources that contain JSF components. Default is '.jsp'. </description> <param-name>javax.faces.DEFAULT_SUFFIX</param-name> <param-value>.jsp</param-value> </context-param> <context-param> <description>These elements define the skin you want to use in your application </description> <param-name>org.richfaces.SKIN</param-name> <param-value>classic</param-value> </context-param> <context-param> <description> If false, client data will not be encoded, allowing multiple portlets on a page to share the same client data model. By default, client data will be encoded, so any value other than "false", or the absence of the parameter, will result in client data being encoded. This also affects using Page Data with the Chart or Data Tree. By default Page Data is encoded. Setting this value to "false" will also unencode any Page Data that is being used with either a Chart or a Data Tree.</description> <param-name>com.ibm.faces.ENCODE_DATA</param-name> <param-value>true</param-value> </context-param> <context-param> <description> When using Ajax components with Websphere Portal server 5.1 (versions 5.1.0.3 onwards), this value must be set to true.</description> <param-name>com.ibm.faces.TURN_OFF_AJAX_PORTAL_60_PATH</param-name> <param-value>false</param-value> </context-param> <filter> <display-name>RichFaces Filter</display-name> <filter-name>richfaces</filter-name> <filter-class>org.ajax4jsf.Filter</filter-class> </filter> <filter-mapping> <filter-name>richfaces</filter-name> <servlet-name>Faces Servlet</servlet-name> <dispatcher>FORWARD</dispatcher> <dispatcher>INCLUDE</dispatcher> <dispatcher>REQUEST</dispatcher> </filter-mapping> <servlet id="Servlet_1202943242218"> <servlet-name>JS Resource Servlet</servlet-name> <servlet-class> com.ibm.faces.webapp.JSResourceServlet </servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet id="Servlet_1202943242500"> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>JS Resource Servlet</servlet-name> <url-pattern>/.ibmjsfres/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>/faces/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>*.faces</url-pattern> </servlet-mapping>
Project 2:
<lifecycle> <phase-listener>com.ibm.faces.webapp.ValueResourcePhaseListener</phase-listener> </lifecycle> <!-- variable/property resolver registration --> <application> <state-manager> com.ibm.faces.application.DevelopmentStateManager</state-manager> <property-resolver>com.ibm.faces.databind.SelectItemsPropResolver</property-resolver> <variable-resolver>com.ibm.faces.databind.SelectItemsVarResolver</variable-resolver> <variable-resolver>org.springframework.web.jsf.DelegatingVariableResolver</variable-resolver> <message-bundle>/WEB-INF/conf/mensajes/messageResource</message-bundle> <locale-config> <default-locale>es_MX</default-locale> </locale-config> </application> <validator> <description> Validator que utilizado para la cetificacion de los datos del negocio </description> <validator-id>validatorProfuturo</validator-id> <validator-class>mx.com.profuturo.mit.infraestructura.validator.ValidatorProfuturo</validator-class> <property> <property-name>serviceLocator</property-name> <property-class>mx.com.profuturo.mit.infraestructura.util.ServiceLocatorImpl</property-class> </property> </validator>
<context-param> <description> The location where state information is saved. Valid values are 'server' (typically saved in HttpSession) and 'client' (typically saved as a hidden field in the form. Default is server. </description> <param-name>javax.faces.STATE_SAVING_METHOD</param-name> <param-value>server</param-value> </context-param> <context-param> <description> Comma-delimited list of context-relative resource paths under which the JSF implementation will look for application configuration resources, before loading a configuration resource named /WEB-INF/facesconfig.xml (if such a resource exists). </description> <param-name>javax.faces.CONFIG_FILES</param-name> <param-value></param-value> </context-param> <context-param> <description> The default suffix for extension-mapped resources that contain JSF components. Default is '.jsp'. </description> <param-name>javax.faces.DEFAULT_SUFFIX</param-name> <param-value>.jsp</param-value> </context-param> <context-param> <description> Number of Views to be stored in the session when Server-Side State Saving is being used. Default is 15. </description> <param-name> com.sun.faces.numberOfViewsInSession </param-name> <param-value>15</param-value> </context-param> <context-param> <description> If set to true while server-side state saving is being used, a serialized representation of the view is stored on the server. This allows for failover and sever clustering support. Default is false. This parameter is not available in JSF 1.0. </description> <param-name>com.sun.faces.enableHighAvailability</param-name> <param-value>false</param-value> </context-param> <context-param> <description> If set to true while client-side state saving is being used, reduces the number of bytes sent to the client by compressing the state before it is encoded and written as a hidden field. Default is false. This parameter is not available in JSF 1.0. </description> <param-name>com.sun.faces.compressViewState</param-name> <param-value>false</param-value> </context-param> <context-param> <description> Monitors Faces JSP files for modifications and synchronizes a running server with the changes without restarting the server. If this parameter is set to false or removed from the deployment descriptor, any changes made to Faces JSP files may not be seen by the server until it is restarted. This parameter is usually set to true while the Faces JSP files are being developed and debugged in order to improve the performance of the development environment. </description> <param-name>com.ibm.ws.jsf.JSP_UPDATE_CHECK</param-name> <param-value>true</param-value> </context-param> <context-param> <description> Load JSF runtime when the application server starts up. If this parameter is set to false or removed, JSF runtime will be loaded and initialized when the first JSF request is processed. This may disable custom JSF extensions, such as factories defined in the project. </description> <param-name> com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP </param-name> <param-value>true</param-value> </context-param> <context-param> <description> If set to true disables use of MultipartFacesContext, allowing underlying implementations to be used. MultipartFacesContext is required when the FileUpload component is used, and can be disabled otherwise. </description> <param-name> com.ibm.faces.DISABLE_JWL_MULTIPART_CONTEXT </param-name> <param-value>false</param-value> </context-param> <context-param> <description> Value, in milliseconds, to be used for Expires header for resources served by the JavaScript Resource Servlet. Default is never (31536000000 milliseconds or 1 year). </description> <param-name>com.ibm.faces.RESOURCE_EXPIRE_MS</param-name> <param-value>31536000000</param-value> </context-param> <context-param> <description> Defines the strictness of the conversion when converting from a string to a date. The higher the value, the more exactly the value must conform to the format. If 0 (liberal), all 'literals' are ignored while parsing a value, mis-ordered components will be rearranged, any missing component is supplied using the current datetime, misspellings and incomplete spellings are allowed (to the extent that they can be evaluated), 'E' and other non-unique components are ignored. If 1 (strict), all 'literals' are ignored while parsing a value, any missing component is supplied using the current datetime, misspellings and incomplete spellings are allowed (to the extent that they can be evaluated), 'E' and other non-unique components are ignored. For example if the pattern is MMMM dd, yyyy a user can enter 'Feb/02/04' and it will be parsed as February 02, 2004. If 2 (very strict), an exact match is required except long month names can be 'shortened' to the minimum number of unique characters and 'E' and other non-unique components are ignored. Literals must match exactly. Default is 1. </description> <param-name> com.ibm.faces.DATETIME_ASSIST_STRICTNESS </param-name> <param-value>1</param-value> </context-param> <context-param> <description> Defines the strictness of the conversion when converting from a string to a number. The higher the value, the more exactly the value must conform to the pattern. For numbers, currently strictness levels of 0 and 1 are equivalent. If the strictness is 2, if number is signed, the sign must be provided (otherwise it's assumed positive). Default is 1. </description> <param-name>com.ibm.faces.NUMBER_ASSIST_STRICTNESS</param-name> <param-value>1</param-value> </context-param> <context-param> <description> Defines the path for resources such as JavaScript libraries and images. The value can be either: 1. An empty string. Context path of the current application will be used. 2. A path string. Example: /project13. A number. Specifies the number of nodes to use from the context path starting from the left. Example: With a value of 1 if the context path is /screen/faces/SSID110267549/RID1102676 the path will be evaluated as /screen Default is an empty string. </description> <param-name> com.ibm.faces.USE_UNENCODED_CONTEXT_PATH </param-name> <param-value></param-value> </context-param> <context-param> <description> Sets a custom url-pattern for the JavaScript Resource servlet. Should match servlet mapping setting for the JavaScript Resource servlet. If the default default mapping value '/.ibmjsfres/*' is modified, this context-param should also be modified. </description> <param-name> com.ibm.faces.JS_RESOURCE_SERVLET_URL_PATTERN </param-name> <param-value>/.ibmjsfres/*</param-value> </context-param> <context-param> <description> If set to true, forces JavaScript Resource Servlet to cache all resources on the server. This can be useful when client-side caching is turned off. </description> <param-name>com.ibm.faces.JS_RESOURCE_SERVLET_CACHE</param-name> <param-value>false</param-value> </context-param> <context-param> <description> Sets a custom charset mapping properties file similar to converter.properties in WAS. </description> <param-name>com.ibm.faces.ENCODING_MAPPING</param-name> <param-value>converter.properties</param-value> </context-param> <context-param> <description> Number of Views to be stored in the session when Enhanced State Saving is being used. Default is 15. </description> <param-name> com.ibm.faces.ENHANCED_SERVER_STATE_SAVING_SESSION_STORED_VIEWS </param-name> <param-value>15</param-value> </context-param> <context-param> <description> If set to true, the entire JavaScript library, containing code for all components, will be included in the generated pages as one file. If set to false or removed, multiple smaller JavaScript files will be included, depending on the components used on the page.Default is false. </description> <param-name>com.ibm.faces.USE_HXCLIENT_FULL</param-name> <param-value>false</param-value> </context-param> <!--Inicia la Configuracion del contexto de Spring--> <context-param> <param-name>contextConfigLocation</param-name> <param-value>/WEB-INF/conf/applicationContext.xml</param-value> </context-param> <!--termina la Configuracion del contexto de Spring--> <!-- RichFase Skin configuration --> <context-param> <param-name>org.richfaces.SKIN</param-name> <param-value>blueSky</param-value> </context-param> <!-- FIN SKIN--> <!-- RichFase Filter --> <filter> <display-name>RichFaces Filter</display-name> <filter-name>richfaces</filter-name> <filter-class>org.ajax4jsf.Filter</filter-class> </filter> <filter-mapping> <filter-name>richfaces</filter-name> <servlet-name>Faces Servlet</servlet-name> <dispatcher>REQUEST</dispatcher> <dispatcher>FORWARD</dispatcher> <dispatcher>INCLUDE</dispatcher> </filter-mapping> <!-- FIN FILTER RICHFACES --> <context-param> <description> If false, client data will not be encoded, allowing multiple portlets on a page to share the same client data model. By default, client data will be encoded, so any value other than "false", or the absence of the parameter, will result in client data being encoded. This also affects using Page Data with the Chart or Data Tree. By default Page Data is encoded. Setting this value to "false" will also unencode any Page Data that is being used with either a Chart or a Data Tree.</description> <param-name>com.ibm.faces.ENCODE_DATA</param-name> <param-value>true</param-value> </context-param> <context-param> <description> When using Ajax components with Websphere Portal server 5.1 (versions 5.1.0.3 onwards), this value must be set to true.</description> <param-name>com.ibm.faces.TURN_OFF_AJAX_PORTAL_60_PATH</param-name> <param-value>false</param-value> </context-param> <listener> <listener-class> com.sun.faces.config.ConfigureListener </listener-class> </listener> <servlet id="Servlet_1222268675937"> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet id="Servlet_1222268679609"> <servlet-name>JavaScript Resource Servlet</servlet-name> <servlet-class> com.ibm.faces.webapp.JSResourceServlet </servlet-class> <load-on-startup>-1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>/faces/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>*.faces</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>JavaScript Resource Servlet</servlet-name> <url-pattern>/.ibmjsfres/*</url-pattern> </servlet-mapping> <welcome-file-list> <welcome-file>index.html</welcome-file> <welcome-file>index.htm</welcome-file> <welcome-file>index.jsp</welcome-file> <welcome-file>default.html</welcome-file> <welcome-file>default.htm</welcome-file> <welcome-file>default.jsp</welcome-file> </welcome-file-list>
-
faces-config.xml2.zip 8.0 KB
-
web.xml2.zip 4.2 KB
-
faces-config.xml 103.9 KB
-
web.xml 13.9 KB