首頁 > 開發者 > Ajax

Converting a JSF 1.2 application to JSF 2.0 – Facelets and Ajax

來源：互聯網
上載者：User
創建阿里雲帳戶，並獲得超過 40 款產品的免費試用版；而企業帳戶則可以享有總值 $1200 的免費試用版。立即註冊！
TOTD
#47 showed how to deploy a JSF 1.2 application (using
Facelets and Ajax/JSF Extensions) on Mojarra
2.0-enabled GlassFish.
 In this blog we'll use new features added in JSF 2.0 to
simplify our
application:
  • Use integrated
    Facelets and resource
    re-location to simplify our facelets
  • Replace JSF Extensions Ajax API with new in-built
    JavaScript APIs to expose Ajax functionality.

Let's get started!

  • Re-create the app as defined in TOTD
    #47. This app is built using JSF 1.2 core components and
    Facelets. It uses JSF Extensions for adding Ajax capabilities. Lets
    change this app to use newer features of JSF 2.0.
  • Edit "faces-config.xml" and change the value of
    faces-config/@version from "1.2" to "2.0".
  • Remove the following fragment from "faces-config.xml":
       
    <application>
           
    <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
        </application>

    This fragment is no longer required because Facelets is the default
    view technology in JSF 2.0. But it's important to remember that JSF 2.0
    Facelets is disabled by default if "WEB-INF/faces-config.xml" is
    versioned at 1.2 or older.

  • Remove the following code fragment from "web.xml":
           
    <init-param>
             
    <param-name>javax.faces.LIFECYCLE_ID</param-name>
             
    <param-value>com.sun.faces.lifecycle.PARTIAL</param-value>
           
    </init-param>

    This is only required if JSF Extensions APIs are used.

  • Edit "welcome.xhtml" and replace code with:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
    Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml"
         
    xmlns:ui="http://java.sun.com/jsf/facelets"
         
    xmlns:h="http://java.sun.com/jsf/html">
        <ui:composition>
            <h:head>
               
    <h1><h:outputText value="What city do you like ?"
    /></h1>
            </h:head>
           
            <h:body>
               
    <h:form prependId="false">
                   
    <h:panelGrid columns="2">
                       
    <h:outputText value="CityName:"/>
                       
    <h:inputText value="#{cities.cityName}"
                                    
    title="CityName"
                                    
    id="cityName"
                                    
    required="true"
                                    
    onkeyup="javax.faces.Ajax.ajaxRequest(this,
    event, { execute: 'cityName', render: 'city_choices'});"/>
                       
    <h:outputText value="CountryName:"/>
                       
    <h:inputText value="#{cities.countryName}" title="CountryName"
    id="countryName" required="true"/>
                   
    </h:panelGrid>
                   

                   
    <h:commandButton action="#{dbUtil.saveCity}"
    value="submit"/>
                   
    <br/><br/>
                   
    <h:outputText id="city_choices"
    value="#{dbUtil.cityChoices}"></h:outputText>
                   

                   
    <br/><br/>
                   
    <h:message for="cityName" showSummary="true" showDetail="false"
    style="color: red"/><br/>
                   
    <h:message for="countryName" showSummary="true"
    showDetail="false" style="color: red"/>
               
    </h:form>
            </h:body>
            <h:outputScript
    name="ajax.js" library="javax.faces" target="header"/>

        </ui:composition>
       
    </html>

    The differences are highlighted in bold and
    explained below:

    • "template.xhtml" is no longer required because standard
      tags are used to identify "head" and "body".
    • <h:head> and <h:body> are new
      tags defined in JSF 2.0. These tags define where the nested
      resources need to be rendered.
    • <h:outputScript> is a new tag defined in
      JSF 2.0 and allows an external JavaScript file to be referenced. In
      this
      case, it is referencing "ajax.js" script and is rendered in "head". The
      script file itself is bundled in "jsf-api.jar" in
      "META-INF/resources/javax.faces" directory. It adds Ajax
      functionality to the application.
    • "javax.faces.Ajax.ajaxRequest" function is defined in the
      JavaScript file "ajax.js". This particular function invocation ensures
      that "city_choices" is
      rendered when execute
      portion of the request lifecycle is executed for "cityName" field. The
      complete documentation is available in "ajax.js". Read more
      details about what happens in the background here.

    • Notice how the Facelet is so simplified.

  • Refactor "result.xhtml" such that the code looks like as
    shown below:

    The changes are explained in the previous step, basically a clean
    Facelet using standard <h:head> and
    <h:body> tags and everything else remains as is.

And that's it, just hit "Undeploy and Deploy" in NetBeans IDE and your
application should now get deployed on Mojarra 2.0-enabled GlassFish.
To reiterate, the main things highlighted in this blog are:

  • Facelets are integrated in Mojarra 2.0.
  • New tags for resource re-location allow a simpler and
    cleaner facelet embedded in a JSF application.
  • JavaScript APIs provide a clean way to expose Ajax
    functionality in JSF app.

And all of these features are defined in the JSF 2.0 specification. So
if you are using Mojarra then be assured that you are developing a
standards compliant user interface.

Have you tried your JSF 1.2 app on Mojarra 2.0 ? Drop a comment on this
blog if you have.

File JSF related bugs here
using "2.0.0 EDR1" version and ask your questions on webtier@glassfish.dev.java.net.

Please leave suggestions on other TOTD (Tip Of The Day) that
you'd like to see.
An archive of all the tips is available here.

轉自：http://server.dzone.com/blogs/arungupta/2008/10/15/totd-48-converting-a-jsf-12-ap

本文章原先以中文撰寫並發佈於 aliyun.com，亦設英文版本，僅作資訊用途。本網站不對文章的準確性，完整性或可靠性或其任何翻譯作出任何明示或暗示的陳述或保證。如對該文章有任何疑慮或投訴，請傳送電郵至 info-contact@alibabacloud.com 並提供相關疑慮或投訴的詳細說明。職員會於 5 個工作天內與您聯絡，一經驗證之後，即會刪除該侵權內容。

相關關鍵詞：
jsf 2 2 book jsf file converter jsf tutorial pdf ajax chat application converting hdmi to dvi converting hex to rgb converting to hexadecimal
相關文章
ajax入門指南（二）
ajax使用_雜類
jQuery ajax 檔案下載_ajax
AJAX各種實現方式比較_ajax
AJAX入門--- XMLHttpRequest對象的屬性和方法
解決spring-security session逾時 Ajax 請求沒有重新導向的問題

聯繫我們

該頁面正文內容均來源於網絡整理，並不代表阿里雲官方的觀點，該頁面所提到的產品和服務也與阿里云無關，如果該頁面內容對您造成了困擾，歡迎寫郵件給我們，收到郵件我們將在5個工作日內處理。

如果您發現本社區中有涉嫌抄襲的內容，歡迎發送郵件至： info-contact@alibabacloud.com 進行舉報並提供相關證據，工作人員會在 5 個工作天內聯絡您，一經查實，本站將立刻刪除涉嫌侵權內容。

熱門內容

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

Get Started for Free

  • Sales Support

    1 on 1 presale consultation

    Chat Contact Sales

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

    Open a Ticket

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.

    Learn More