📄 2.mht
字号:
From: <由 Microsoft Internet Explorer 5 保存>
Subject: Tutorial for building J2EE Applications using JBOSS and ECLIPSE
Date: Sun, 5 Dec 2004 12:00:35 +0800
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_NextPart_000_03AB_01C4DAC2.078D5530";
type="text/html"
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
This is a multi-part message in MIME format.
------=_NextPart_000_03AB_01C4DAC2.078D5530
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Location: http://www.tusc.com.au/tutorial/html/chap2.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Tutorial for building J2EE Applications using JBOSS =
and ECLIPSE</TITLE>
<META http-equiv=3DCONTENT-TYPE content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1479" name=3DGENERATOR>
<META content=3D"Glen McCallum and Vishal Sharma" name=3DAUTHOR>
<META content=3D20030729;9513900 name=3DCREATED>
<META content=3DVishal name=3DCHANGEDBY>
<META content=3D20031118;15354000 name=3DCHANGED>
<META=20
content=3D"Tutorial for building J2EE Applications using Eclipse, =
Lomboz, Jboss and Xdoclet."=20
name=3DDESCRIPTION>
<META=20
content=3D"J2EE, Traininig,Tutorial, J2EE, Lomboz, Eclipse, Jboss, =
Xdoclet, J2EE Patterns, EJB, Servlets, JSP, BMP, CMP, Session, =
Configuration, DAO"=20
name=3DKEYWORDS>
<META content=3D"14 days" name=3Drevisit-after><!-- Meta tags --><!-- =
Copyright =A9 2003 TUSC. All rights reserved.--><!--- Header --></HEAD>
<BODY lang=3Den-US dir=3Dltr>
<FORM name=3DsearchForm action=3D../../../../search/index.php =
method=3Dpost>
<TABLE style=3D"PAGE-BREAK-BEFORE: always" cellSpacing=3D0 =
cellPadding=3D4 width=3D957=20
bgColor=3D#0a6a91 border=3D0>
<COLGROUP>
<COL width=3D154>
<COL width=3D276>
<COL width=3D21>
<COL width=3D43>
<COL width=3D119>
<COL width=3D31>
<COL width=3D50>
<COL width=3D178>
<COL width=3D14>
<TBODY>
<TR>
<TD vAlign=3Dtop width=3D154>
<P><A href=3D"http://www.tusc.com.au./contact_us.php"><IMG =
height=3D125=20
alt=3DTUSC=20
=
src=3D"http://www.tusc.com.au/tutorial/images/header/tuscJ2eeLogo.gif"=20
width=3D149 align=3Dbottom border=3D0 =
name=3DGraphic1></A></P></TD>
<TD vAlign=3Dtop width=3D276>
<P><IMG height=3D73 alt=3D"Reliable, On-Time Delivery."=20
src=3D"http://www.tusc.com.au/tutorial/images/header/reliable.gif" =
width=3D268=20
align=3Dbottom border=3D0 name=3DGraphic2><!--search table =
--></P></TD>
<TD width=3D21></TD>
<TD width=3D43>
<P><IMG height=3D9 alt=3DSearch=20
src=3D"http://www.tusc.com.au/tutorial/images/elements/search.gif" =
width=3D41=20
align=3Dbottom border=3D0 name=3DGraphic3></P></TD>
<TD width=3D119>
<P><INPUT maxLength=3D50 size=3D12 name=3DKEYWORD></P></TD>
<TD width=3D31>
<P><INPUT type=3Dimage height=3D18 width=3D29=20
src=3D"http://www.tusc.com.au/tutorial/images/btns/go.gif" =
align=3Dbottom=20
name=3Dgo><INPUT type=3Dhidden value=3DY =
name=3DSECTION_ALL></P></TD>
<TD vAlign=3Dtop width=3D50>
<P><IMG height=3D73 alt=3DSpacer=20
src=3D"http://www.tusc.com.au/tutorial/images/invis.gif" =
width=3D50=20
align=3Dbottom border=3D0 name=3DGraphic5></P></TD>
<TD vAlign=3Dtop width=3D154>
<P><A href=3D"http://www.tusc.com.au./contact_us.php"><IMG =
height=3D125=20
alt=3DTUSC=20
=
src=3D"http://www.tusc.com.au/tutorial/images/header/tuscJ2eeLogo.gif"=20
width=3D149 align=3Dbottom border=3D0 =
name=3DGraphic1></A></P></TD>
<TD width=3D14>
<P><IMG height=3D10 alt=3Dspacer=20
src=3D"http://www.tusc.com.au/tutorial/images/invis.gif" =
width=3D14=20
align=3Dbottom border=3D0 name=3DGraphic58> =
</P></TD></TR></TBODY></TABLE></FORM>
<P><!--- Header finished --><BR><BR></P>
<H2 align=3Dcenter>Tutorial for building J2EE Applications using JBOSS =
and ECLIPSE=20
<IMG height=3D2 =
src=3D"http://www.tusc.com.au/tutorial/images/redrulr5.gif"=20
width=3D775 align=3Dmiddle border=3D0 name=3DGraphic1></H2>
<P><BR><BR></P>
<H1>Chapter 2. </H1>
<P><IMG height=3D2 =
src=3D"http://www.tusc.com.au/tutorial/images/blurulr6.gif"=20
width=3D785 align=3Dmiddle border=3D0 name=3DGraphic2></P>
<H2>Overview Of J2EE Technology and Concepts</H2>
<P>The Java 2 Enterprise Edition (J2EE) is a multitiered architecture =
for=20
implementing enterprise-class applications and web based applications. =
This=20
technology supports a variety of application types from large scale web=20
applications to small client server applications. The main aim of J2EE=20
technology is to create a simple development model for enterprise =
applications=20
using component based application model. In this model such components =
use=20
services provided by the container, which would otherwise typically need =
to be=20
incorporated in application code. Note this may not be ideal in all =
scenarios:=20
for example, a small scale application might be a better fit for a =
light-weight=20
Java technology solution (e.g. Servlets, JSPs, etc.). </P>
<H3>J2EE Components :</H3>
<P>J2EE applications are made up of different components. A J2EE =
component is a=20
self-contained functional software unit that is assembled into a J2EE=20
application with its helper classes and files and that communicates with =
other=20
components in the application. The J2EE specification defines the =
following J2EE=20
components:</P>
<P><B>Application clients and applets are components that run on the=20
client.</B></P>
<P><B>Java Servlet and JavaServer Pages technology components are Web =
components=20
that run on the web server.</B> </P>
<P><B>Enterprise JavaBeans components (enterprise beans) are business =
components=20
that run on the application server.</B></P>
<P><IMG height=3D397=20
src=3D"http://www.tusc.com.au/tutorial/images/chap2/J2EEMultitiredApplica=
tionDiagram.png"=20
width=3D683 align=3Dleft border=3D0 name=3DGraphic3><BR =
clear=3Dleft><BR><BR></P>
<P>All these J2EE components are assembled into a J2EE application, =
verified to=20
be well formed and in compliance with the J2EE specification, and =
deployed to=20
production, where they are run and managed by the J2EE application =
server. </P>
<P><B>In addition to these primary components, it includes standard =
services and=20
supporting technologies which are :</B></P>
<P><B>Java Database Connectivity (JDBC) technology provides access to =
relational=20
database systems.</B></P>
<P><B>Java Transaction API (JTA) or Java Transaction Service (JTS) =
provides=20
transaction support for J2EE components.</B></P>
<P><B>Java Messaging Service (JMS) for asynchronous communication =
between J2EE=20
components. </B></P>
<P><B>Java Naming and Directory Interface (JNDI) provides naming and =
directory=20
access.</B></P>
<P><FONT color=3D#800000><I>Note : All J2EE components are written in =
the Java=20
programming language</I></FONT></P>
<H3><BR><BR></H3>
<H3>J2EE Clients : </H3>
<P>There are normally two types of J2EE client: a Web client and an =
Application=20
client as shown above in figure.</P>
<P>A Web client consists of two parts, dynamic Web pages containing =
various=20
types of markup language (HTML, XML and others), which are generated by =
Web=20
components running in the Web tier, and a Web browser, which draws the =
pages=20
received from the server. Another category of web clients are sometimes =
called=20
as thin client. Thin clients usually do not do things like query =
databases,=20
execute complex business rules, or connect to any legacy applications. =
When we=20
use a thin client, heavyweight operations like these are handled by =
enterprise=20
beans executing on the J2EE server where they can leverage the security, =
speed,=20
services, and reliability of J2EE server-side technologies. </P>
<P>A Web page received from the Web tier can include an embedded applet. =
An=20
applet is a small client application written in the Java programming =
language=20
that executes in the Java virtual machine installed in the Web browser. =
However,=20
client systems will need the Java Plug-in and possibly a security policy =
file in=20
order to execute applets successfully in the Web browser. Web components =
are=20
often a preferred API for creating a Web client program because no =
plug-ins or=20
security policy files are needed on the client systems. Moreover this =
allows=20
cleaner and more modular application design because they provide a means =
to=20
separate application logic from Web page design.</P>
<P>An Application client runs on a client machine and provides a way for =
users=20
to handle tasks that require a richer user interface than can be =
provided by a=20
markup language. It normally has a graphical user interface (GUI) =
created using=20
the Swing or Abstract Window Toolkit (AWT) APIs. Application clients =
directly=20
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -