Myfaces上下文参数英文.doc

SummaryBelow is the list of available web context parameters supported: Web Context ParametersArtifact Id: myfaces-apiNameDefault ValueExpected ValuesSinceDescriptionSource Classjavax.faces.STATE_SAVING_METHODserverserver,client1.1Define the state method to be used. There are two different options defined by the specification: client and server state. When client state is configured, all state information required to create the tree is embedded within the data rendered to the client. Note that because data received from a remote client must always be treated as tainted, care must be taken when using such data. Some StateManager implementations may use encryption to ensure that clients cannot modify the data, and that the data received on postback is therefore trustworthy. When server state is configured, the data is saved somewhere on the back end, and (at most) a token is embedded in the data rendered to the user. javax.faces.application.StateManagerjavax.faces.DEFAULT_SUFFIX.jsp1.1Indicate the default suffix to derive the file URI if extension mapping is used.javax.faces.application.ViewHandlerjavax.faces.CONFIG_FILES1.1Comma separated list of URIs of (additional) faces config files. (e.g. /WEB-INF/my-config.xml)See JSF 1.0 PRD2, 10.3.2 Attention: You do not need to put /WEB-INF/faces-config.xml in here.javax.faces.webapp.FacesServletjavax.faces.LIFECYCLE_ID1.1Identify the Lifecycle instance to be used.javax.faces.webapp.FacesServletorg.apache.myfaces.ERROR_HANDLINGtruetrue,false1.2.4Indicate if myfaces is responsible to handle errors. See /myfaces/Handling_Server_Errors for details.javax.faces.webapp.FacesServletorg.apache.myfaces.ERROR_HANDLER1.2.4If you want to choose a different class for handling the exception. The error-handler needs to include the following methods: handleException(FacesContext fc, Exception ex) handleExceptionList(FacesContext facesContext, List exceptionList) handleThrowable(FacesContext facesContext, Throwable ex)javax.faces.webapp.FacesServletorg.apache.myfaces.ERROR_TEMPLATE_RESOURCEMETA-INF/rsc/myfaces-dev-error.xml1.2.4javax.faces.webapp._ErrorPageWriterorg.apache.myfaces.DEBUG_TEMPLATE_RESOURCEMETA-INF/rsc/myfaces-dev-debug.xml1.2.4javax.faces.webapp._ErrorPageWriterArtifact Id: myfaces-implNameDefault ValueExpected ValuesSinceDescriptionSource Classorg.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION201.1Only applicable if state saving method is server (= default). Defines the amount (default = 20) of the latest views are stored in .apache.myfaces.application.jsp.JspStateManagerImplorg.apache.myfaces.SERIALIZE_STATE_IN_SESSIONtrue1.1Only applicable if state saving method is server (= default). If true (default) the state will be serialized to a byte stream before it is written to the session. If false the state will not be serialized to a byte .apache.myfaces.application.jsp.JspStateManagerImplorg.apache.myfaces.COMPRESS_STATE_IN_SESSIONtrue1.1Only applicable if state saving method is server (= default) and if org.apache.myfaces.SERIALIZE_STATE_IN_SESSION is true (= default). If true (default) the serialized state will be compressed before it is written to the session. If false the state will not be .apache.myfaces.application.jsp.JspStateManagerImplorg.apache.myfaces.CACHE_OLD_VIEWS_IN_SESSION_MODEoffoff, no, hard-soft, soft, soft-weak, weak1.2.5Define the way of handle old view references(views removed from session), making possible to store it in a cache, so the state manager first try to get the view from the session. If is it not found and soft or weak ReferenceMap is used, it try to get from it. Only applicable if state saving method is server (= default). The gc is responsible for remove the views, according to the rules used for soft, weak or phantom references. If a key in soft and weak mode is garbage collected, its values are purged. By default no cache is used, so views removed from session became phantom references. off, no: default, no cache is used hard-soft: use an ReferenceMap(AbstractReferenceMap.HARD, AbstractReferenceMap.SOFT) soft: use an ReferenceMap(AbstractReferenceMap.SOFT, AbstractReferenceMap.SOFT, true) soft-weak: use an ReferenceMap(AbstractReferenceMap.SOFT, AbstractReferenceMap.WEAK, true) weak: use an ReferenceMap(AbstractReferenceMap.WEAK, AbstractReferenceMap.WEAK, true) org.apache.myfaces.application.jsp.JspStateManagerImplorg.apache.myfaces.config.annotation.LifecycleProvider1.1org.apache.myfaces.config.annotation.DefaultLifecycleProviderFactoryorg.apache.myfaces.EL_RESOLVER_COMPARATOR1.2.10, 2.0.2org.apache.myfaces.el.unified.ResolverBuilderBaseorg.apache.myfaces.PRETTY_HTMLtruetrue,false1.1If true, rendered HTML code will be formatted, so that it is human readable. i.e. additional line separators and whitespace will be written, that do not influence the HTML code. Default: trueorg.apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.ALLOW_JAVASCRIPTtruetrue,false1.1This parameter tells MyFaces if javascript code should be allowed in the rendered HTML output. If javascript is allowed, command_link anchors will have javascript code that submits the corresponding form. If javascript is not allowed, the state saving info and nested parameters ill be added as url parameters. Default: trueorg.apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.DETECT_JAVASCRIPTfalsetrue,false1.1org.apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.AUTO_SCROLLfalsetrue,false1.1If true, a javascript function will be rendered that is able to restore the former vertical scroll on every request. Convenient feature if you have pages with long lists and you do not want the browser page to always jump to the top if you trigger a link or button action that stays on the same page. Default: falseorg.apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.ADD_RESOURCE_CLASSorg.apache.myfaces.renderkit.html.util.DefaultAddResource1.1Tomahawk specific: A class implementing the org.apache.myfaces.shared_impl.renderkit.html.util.AddResource interface. It is responsible to place scripts and css on the right position in your HTML document. Default: org.apache.myfaces.shared_impl.renderkit.html.util.DefaultAddResource Follow the description on the MyFaces-Wiki-Performance page to enable StreamingAddResource instead of DefaultAddResource if you want to gain .apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.CHECK_EXTENSIONS_FILTERtruetrue,false1.1Tomahawk specific: A very common problem in configuring MyFaces-web-applications is that the Extensions-Filter is not configured at all or improperly configured. This parameter will check for a properly configured Extensions-Filter if it is needed by the web-app. In most cases this check will work just fine, there might be cases where an internal forward will bypass the Extensions-Filter and the check will not work. If this is the case, you can disable the check by setting this parameter to .apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTStruetrue,false1.1org.apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.CONFIG_REFRESH_PERIOD21.1org.apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.VIEWSTATE_JAVASCRIPTfalsetrue,false1.1org.apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.RENDER_VIEWSTATE_IDtruetrue,false1.1org.apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.STRICT_XHTML_LINKStruetrue,false1.1org.apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.RENDER_CLEAR_JAVASCRIPT_FOR_BUTTONfalsetrue,false1.2.3This param renders the clear javascript on button necessary only for compatibility with hidden fields feature of myfaces. This is done because jsf ri does not render javascript on onclick method for button, so myfaces should do .apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.RENDER_HIDDEN_FIELDS_FOR_LINK_PARAMSfalsetrue,false1.2.9This param renders hidden fields at the end of h:form for link params when h:commandLink + f:param is used, instead use javascript to create them. Set this param to true also enables org.apache.myfaces.RENDER_CLEAR_JAVASCRIPT_FOR_BUTTON automatically to ensure consistency. This feature is required to support Windows Mobile 6, because in this environment, document.createElement() and form.appendChild() javascript methods are not .apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.SAVE_FORM_SUBMIT_LINK_IEfalsetrue,false1.1Add a code that save the form before submit using a link (call to window.external.AutoCompleteSaveForm(form) ). Its a bug on IE.org.apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.DELEGATE_FACES_SERVLET1.2.7org.apache.myfaces.shared_impl.config.MyfacesConfigorg.apache.myfaces.USE_ENCRYPTIONtruetrue,false1.1Indicate if the view state is encrypted or not. By default, encryption is .apache.myfaces.shared_impl.util.StateUtilsorg.apache.myfaces.SECRET1.1Defines the secret (Base64 encoded) used to initialize the secret key for encryption algorithm. See MyFaces wiki/web site documentation for instructions on how to configure an application for different encryption .apache.myfaces.shared_impl.util.StateUtilsorg.apache.myfaces.ALGORITHMDES1.1Indicate the encryption algorithm used for encrypt the view .apache.myfaces.shared_impl.util.StateUtilsorg.apache.myfaces.SECRET.CACHE1.1If is set to false, the secret key used for encryption algorithm is not cached. This is used when the returned SecretKey for encryption algorithm is not thread .apache.myfaces.shared_impl.util.StateUtilsorg.apache.myfaces.ALGORITHM.IV1.1Defines the initialization vector (Base64 encoded) used for the encryption algorithmorg.apache.myfaces.shared_impl.util.StateUtilsorg.apache.myfaces.ALGORITHM.PARAMETERSECB/PKCS5Padding1.1Defines the default mode and padding used for the encryption algorithmorg.apache.myfaces.shared_impl.util.StateUtilsorg.apache.myfaces.SERIAL_FACTORY1.1Defines the factory class name using for serialize/deserialize the view state returned by state manager into a byte array. The expected class