protected Status getDialogStatus() {
Map sessionMap = FacesContext.getCurrentInstance() .getExternalContext() .getSessionMap(); return(Status)sessionMap.get(org.apache.shale.dialog.Globals.STATUS);
}session map code2:
ChartData data = new ChartData(); data.setWidth(width); data.setHeight(height); data.setTitle(title); data.setNames(names); data.setValues(values); String id = component.getClientId(context); ExternalContext external = FacesContext.getCurrentInstance().getExternalContext(); Map<String, Object> session = external.getSessionMap(); session.put(id, data);灝哋bject 淇濆瓨鍦╯essionscope map 閲岋紝鍙互鍦ㄩ〉闈㈠鑸埌鍏朵粬欏甸潰鏃訛紝榪樿兘緇х畫璁塊棶Object銆?br /> requestMap鎴杝essionMap 涓存椂淇濆瓨瀵硅薄銆?
]]>
<html> <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %> <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %> <%@ taglib uri="http://corejsf.com/pager" prefix="corejsf" %> <f:view> <head> <link href="styles.css" rel="stylesheet" type="text/css"/> <title>Pager Test</title> </head> <body> <h:form> <h:dataTable id="timezones" value="#{bb.data}" var="row" rows="10"> <h:column> <h:selectBooleanCheckbox value="{bb.dummy}" onchange="submit()"/> </h:column> <h:column> <h:outputText value="#{row}" /> </h:column> </h:dataTable> <corejsf:pager dataTableId="timezones" showpages="20" selectedStyleClass="currentPage"/> <h:commandButton value="foo"/> </h:form> </body> </f:view> </html>
onchange="submit()"
]]>
2.Call FacesContext.renderResponse() to skip the rest of the life cycle up to Render Response.
3.Call FacesContext.responseComplete() to skip the rest of the life cycle entirely.
See "Immediate Components" on page 287 for an example of using FacesContext.renderResponse().
private static final String US = "United States"; 
public void countryChanged(ValueChangeEvent event) { FacesContext context = FacesContext.getCurrentInstance(); if (US.equals((String) event.getNewValue())) context.getViewRoot().setLocale(Locale.US); else context.getViewRoot().setLocale(Locale.CANADA); context.renderResponse(); }The call to renderResponse() skips the rest of the life cycle鈥攊ncluding validation of the rest of the input components in the form鈥攗p to Render Response. Thus, the other validations are skipped and the response is rendered normally (in this case, the current page is redisplayed).
To summarize, you can skip validation when a value change event fires by doing the following:
-
Adding an immediate attribute to your input tag
-
Calling FacesContext.renderResponse() at the end of your listener
涓婃枃寮曠敤錛氥奵ore JavaServer™ Faces, Second Edition銆?/span>
]]>
| Variable Name | Meaning |
|---|---|
| header | A Map of HTTP header parameters, containing only the first value for each name. |
| headerValues | A Map of HTTP header parameters, yielding a String[]array of all values for a given name. |
| param | A Map of HTTP request parameters, containing only the first value for each name. |
| paramValues | A Map of HTTP request parameters, yielding a String[]array of all values for a given name. |
| cookie | A Map of the cookie names and values of the current request. |
| initParam | A Map of the initialization parameters of this web application. Initialization parameters are discussed in Chapter 10. |
| requestScope | A Map of all request scope attributes. |
| sessionScope | A Map of all session scope attributes. |
| applicationScope | A Map of all application scope attributes. |
| facesContext | The FacesContext instance of this request. This class is discussed in Chapter 6. |
| view | The UIViewRoot instance of this request. This class is discussed in |
Finally, if the name is still not found, it is passed to the VariableResolver of the JSF application. The default variable resolver looks up managed-bean elements in a configuration resource, typically the faces-config.xml file.
Consider, for example, the expression
#{user.password}
The term user is not one of the predefined(棰勫畾涔? objects. When it is encountered錛堥亣鍒幫級 for the first time, it is not an attribute name in request, session, or application scope.
Therefore, the variable resolver processes the faces-config.xml entry:
<managed-bean>
<managed-bean-name>user</managed-bean-name>
<managed-bean-class>com.corejsf.UserBean</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>
The variable resolver calls the default constructor of the class com.corejsf.User-Bean. Next, it adds an association to the sessionScope map. Finally, it returns the object as the result of the lookup.
When the term user needs to be resolved again in the same session, it is located in the session scope
Composite Expressions
You can use a limited set of operators inside value expressions:
Arithmetic operators + - * / %. The last two operators have alphabetic variants div and mod.
Relational operators < <= > >= == != and their alphabetic variants lt le gt ge eq ne. The first four variants are required for XML safety.
Logical operators && || ! and their alphabetic variants and or not. The first variant is required for XML safety.
The empty operator. The expression empty a is true if a is null, an array or String of length 0, or a Collection or Map of size 0.
The ternary ?: selection operator.
Operator precedence follows the same rules as in Java. The empty operator has the same precedence as the unary - and ! operators.
Generally, you do not want to do a lot of expression computation in web pages鈥攖hat would violate the separation of presentation and business logic. However, occasionally, the presentation layer can benefit from operators. For example, suppose you want to hide a component when the hide property of a bean is true. To hide a component, you set its rendered attribute to false. Inverting the bean value requires the ! (or not) operator:
<h:inputText rendered="#{!bean.hide}" ... />
Finally, you can concatenate plain strings and value expressions by placing them next to each other. Consider, for example,
<h:outputText value="#{messages.greeting}, #{user.name}!"/>
The statement concatenates four strings: the string returned from #{messages. greeting}, the string consisting of a comma and a space, the string returned from #{user.name}, and the string consisting of an exclamation mark.
涓婃枃鍑鴻嚜錛氥奵ore JavaServer™ Faces, Second Edition銆?/span>
]]>
<h:selectOneMenu value="#{form.country}" onchange="submit()" valueChangeListener="#{form.countryChanged}"> <f:selectItems value="#{form.countryNames}"/> </h:selectOneMenu>
onchange="submit()"
<f:selectItems value="#{form.countryNames}"/> @ Specifies items for a select one or select many component
]]>
For example, suppose that in our quiz application, the startOverAction returns the string "again" instead of "startOver". The same string can be returned by the answerAction. To differentiate between the two navigation cases, you can use a from-action element. The contents of the element must be identical to the method expression string of the action attribute:
<navigation-case> <from-action>#{quiz.answerAction}</from-action> <from-outcome>again</from-outcome> <to-view-id>/again.jsp</to-view-id> </navigation-case> <navigation-case> <from-action>#{quiz.startOverAction}</from-action> <from-outcome>again</from-outcome> <to-view-id>/index.jsp</to-view-id> </navigation-case>]]>
<web-app> <context-param> <param-name>javax.faces.CONFIG_FILES</param-name> <param-value>WEB-INF/navigation.xml,WEB-INF/beans.xml</param-value> </context-param> </web-app>(This mechanism is attractive for builder tools because it separates navigation, beans, etc.)
beans.xml 錛歮anaged-bean
]]>
Redirecting the page is slower than forwarding because another round trip to the browser is involved. However, the redirection gives the browser a chance to update its address field.
Figure 3-8 shows how the address field changes when you add a redirection element, as follows:
<navigation-case> <from-outcome>success</from-outcome> <to-view-id>/success.jsp</to-view-id> <redirect/></navigation-case>
Without redirection, the original URL (localhost:8080/javaquiz/index.faces) is unchanged when the user moves from the /index.jsp page to the /success.jsp face. With redirection, the browser displays the new URL (localhost:8080/ javaquiz/success.faces).
Tip
 |
Use the redirect element for pages that the user might want to bookmark. |
]]>
鏋勫緩JSF搴旂敤紼嬪簭鏃跺繀欏葷殑鍏抽敭jar鏂囦歡鏄?jsf-api.jar 鍜?jsf-impl.jar 銆?br /> 闄や簡鏍稿績JSF榪愯鏃秊ar鏂囦歡錛岃繕闇瑕佷竴浜涘叧閿殑“鍏叡”jar鏂囦歡錛坈ommons-beanutils.jar commonscollections.jar commons-digester.jar commons-logging.jar 錛?br />
2 standard.jar=local path to JSTL standard.jar
3 jsf-impl.jar=local path to jsf-impl.jar
4
5
7 # Jars for miscellaneous dependencies required #by Sun's JSF 1.1
8 # implementation
9 commons-beanutils.jar=local path to commons-beanutils.jar
10 commons-collections.jar=local path to commons-collections.jar
11 commons-digester.jar=local path to commons-digester.jar
12 commons-logging.jar=local path to commons-logging.jar
]]>