The J2EE(TM) 1.4 Tutorial - The Diigo Meta page

• 06 Jun 09
  

  Ivan Balashov

  Java Books Tutorials

• 17 Dec 08
  

  Vel Rajan

  j2ee Technical

• 01 Dec 08
  

  abdiahmed Ahmed
• 

  Warren Sheaffer

  Good Introductory Material

  • he J2EE application parts shown in Figure 1-1 are presented in J2EE Components.
    

    
    
    • Client-tier components run on the client machine.
    • Web-tier components run on the J2EE server.
    • Business-tier components run on the J2EE server.
    • Enterprise information system (EIS)-tier software runs on the EIS server.

  • XML
    

    
    

    
    XML is a cross-platform, extensible, text-based standard for representing data. When XML data is exchanged between parties, the parties are free to create their own tags to describe the data, set up schemas to specify which tags can be used in a particular kind of XML document, and use XML stylesheets to manage the display and handling of the data.
    

    
    

    
    For example, a web service can use XML and a schema to produce price lists, and companies that receive the price lists and schema can have their own stylesheets to handle the data in a way that best suits their needs. Here are examples:
    

    
    
    • One company might put XML pricing information through a program to translate the XML to HTML so that it can post the price lists to its intranet.
    • A partner company might put the XML pricing information through a tool to create a marketing presentation.
    • Another company might read the XML pricing information into an application for processing.
  • 10 more annotations...
  • • J2EE multitiered applications are generally considered to be three-tiered applications because they are distributed over three locations: client machines, the J2EE server machine, and the database or legacy machines at the back end. Three-tiered applications that run in this way extend the standard two-tiered client and server model by placing a multithreaded application server between the client application and back-end storage.
    • Application clients and applets are components that run on the client.
    • where they are run and managed by the J2EE server.

    • Web Clients
      

      
      

      
      A web client consists of two parts: (1) dynamic web pages containing various types of markup language (HTML, XML, and so on), which are generated by web components running in the web tier, and (2) a web browser, which renders the pages received from the server.
      

    • Application Clients
      

      
      

      
      An application client runs on a client machine and provides a way for users to handle tasks that require a richer user interface than can be provided by a markup language. It typically has a graphical user interface (GUI) created from the Swing or the Abstract Window Toolkit (AWT) API, but a command-line interface is certainly possible.
      

      
      

      
      Application clients directly access enterprise beans running in the business tier. However, if application requirements warrant it, an application client can open an HTTP connection to establish communication with a servlet running in the web tier.
      

    • The JavaBeans Component Architecture
      

      
      

      
      The server and client tiers might also include components based on the JavaBeans component architecture (JavaBeans components) to manage the data flow between an application client or applet and components running on the J2EE server, or between server components and a database. JavaBeans components are not considered J2EE components by the J2EE specification.
      

      
      

      
      JavaBeans components have properties and have get and set methods for accessing the properties. JavaBeans components used in this way are typically simple in design and implementation but should conform to the naming and design conventions outlined in the JavaBeans component architecture.
      

    • Your J2EE application uses a thin browser-based client or thick application client. In deciding which one to use, you should be aware of the trade-offs between keeping functionality on the client and close to the user (thick client) and off-loading as much functionality as possible to the server (thin client). The more functionality you off-load to the server, the easier it is to distribute, deploy, and manage the application; however, keeping more functionality on the client can make for a better perceived user experience.

    • Web Components
      

      
      

      
      J2EE web components are either servlets or pages created using JSP technology (JSP pages). Servlets are Java programming language classes that dynamically process requests and construct responses. JSP pages are text-based documents that execute as servlets but allow a more natural approach to creating static content.
      

    • 
      Business Components
      

      
      

      
      Business code, which is logic that solves or meets the needs of a particular business domain such as banking, retail, or finance, is handled by enterprise beans running in the business tier. Figure 1-4 shows how an enterprise bean receives data from client programs, processes it (if necessary), and sends it to the enterprise information system tier for storage. An enterprise bean also retrieves data from storage, processes it (if necessary), and sends it back to the client program.
      

    • Enterprise Information System Tier
      

      
      

      
      The enterprise information system tier handles EIS software and includes enterprise infrastructure systems such as enterprise resource planning (ERP), mainframe transaction processing, database systems, and other legacy information systems. For example, J2EE application components might need access to enterprise information systems for database connectivity.
      

• 07 Sep 08
  

  srsviews s

  java

• 09 Aug 08
  

  adam wang

  doc j2ee office sun

• 06 Jun 08
  

  Akhilesh Mallik
• 27 May 08
  

  Mike C

  enterprise-apps java

• 11 Apr 08
  

  atin sood
  • Order does make a difference when two templates can apply to the same node. In that case, the one that is defined last is the one that is found and processed.
• 28 Mar 08
  

  pc logger
  • To locate a JDBC resource, for example, an enterprise bean invokes the JNDI lookup method.
  • To avoid collisions with names of other enterprise resources in the JNDI namespace, and to avoid portability problems, all names in a J2EE application should begin with the string java:comp/env
  • 5 more annotations...
  • • Data that is shared between web components and is persistent between invocations of a web application is usually maintained in a database.
    • In the JDBC API, databases are accessed via DataSource objects
    • This hierarchical structure permits better organization of information
    • JNDI lookup method
    • Web applications access a data source using a connection
• 26 Mar 08
  

  Lakshminarayanan Venugopal

  1.4 j2ee tutorial

  • Business-tier components run on the J2EE server
  • Business-tier components run on the J2EE server.
• 23 Mar 08
  

  Sebastian Maliszczak

  j2ee tutorial tutorials

• 14 Feb 08
  

  fibbling

  crash it courses it knowledge bases

• 14 Jan 08
  

  WittyGuy

  j2ee tutorial

• 05 Sep 07
  

  Anne Kathrine Petteroe

  Sun - The J2EE(TM) 1.4 Tutorial

  java tutorials j2ee

• 10 Jul 07
  

  konkorder

  j2ee

• 09 May 07
  

  Prasanth RK

  Tutorial

• 02 May 07
  

  B B

  文档

• 04 Apr 07
  

  cancerian80

  day 8 (j2ee/duke's bank) gcg java links

• 22 Mar 07
  

  Ferdinand Urban

  java

• 08 Nov 06
  

  Bruno Wouters

  development programming server software Tutorials web

• 25 Oct 06
  

  Seth

  j2ee java soap tutorial webservices wsdl xml

• 20 Jun 06
  

  j4link

  Development_Java

• 09 Jun 06
  

  Dinakar

  java tutorial

• 10 Feb 06
  

  Jochen Lillich

  java j2ee tutorial ejb jsf

• 14 Oct 05
  

  Sam Cogan

  Tutorials Java

• 07 Dec 03
  

  mattbert

  GIS Programming Java Imported Bookmarks

Page Comments

• 
  Seth on 2006-10-25
  The J2EE(TM) 1.4 Tutorial is a guide to developing enterprise applications for the Java 2 Platform, Enterprise Edition (J2EE) version 1.4. Here we cover all the things you need to know to make the best use of this tutorial.

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.