2013年Apress《Java EE 7 Recipes》精华指南

Java.EE.7

5星 · 超过95%的资源需积分: 9 130 浏览量更新于2024-07-25 收藏 10.24MB PDF 举报

"Apress.Java.EE.7.Recipes.Jun.2013"是一本专注于Java Enterprise Edition (Java EE) 7技术的实用指南，涵盖了广泛的Java Web开发领域。这本书旨在提供深入且易于理解的解决方案，帮助读者快速掌握和应用Java EE的核心技术。首先，书的前言部分介绍了作者和参与技术审稿的专家，确保了内容的专业性和权威性。全书共分为17章，每个章节都围绕特定主题展开： 1. **第1章：Servlets简介** - 介绍了Servlet的基础概念，包括如何编写和部署这些服务器端的Java应用程序组件，以及它们在处理HTTP请求中的核心作用。 2. **第2章：JavaServer Pages (JSP)** - 深入解析JSP技术，讲解如何利用JSP页面动态生成HTML，结合Java代码实现网页内容的动态生成。 3. **第3章：JavaServer Faces (JSF)** - 介绍JSF的基本原理和使用，包括其组件模型、生命周期管理，以及如何构建用户界面。 4. **第4章：Facelets** - 作为JSF的一种视图技术，Facelets的介绍帮助开发者理解和优化页面设计流程，提高开发效率。 5. **第5章：JSF标准组件** - 详细讲解了JSF库提供的预定义组件，如何使用它们构建高效、一致的用户界面。 6. **第6章：高级JSF和Ajax** - 探讨了AJAX技术在Java EE中的应用，以及如何利用它提升用户体验，实现无刷新的数据交互。 7. **第7章：JDBC编程** - 介绍如何通过Java访问关系数据库，包括连接管理、SQL查询、事务处理等内容。 8. **第8章：对象关系映射 (ORM)** - 讨论ORM工具如Hibernate或TopLink，如何简化数据库操作，降低代码复杂度。 9. **第9章：Enterprise JavaBeans (EJB)** - EJB是企业级Java架构的核心，这里讲解了其基础概念、会话 Bean、消息驱动 Bean等。 10. **第10章：Query API和JPQL** - 介绍如何使用Java Persistence API (JPA) 和Java Persistence Query Language (JPQL) 进行数据库查询。 11. **第11章：Oracle's GlassFish** - 以Oracle的Java EE应用服务器为例，展示了如何部署和管理Java EE应用。 12. **第13章：Contexts and Dependency Injection (CDI)** - CDI是Java EE的一项关键特性，探讨了依赖注入的概念及其在现代企业应用中的重要性。 13. **第14章：Authentication and Security** - 详细介绍Java EE的安全模型，包括身份验证、授权和数据加密等方面。 14. **第15章：Java Web Services** - 讲解如何创建、部署和调用Web服务，以及RESTful API的设计原则。 15. **第16章：使用其他编程语言的企业解决方案** - 提供了跨平台的开发策略，讨论如何利用Python、Ruby等非Java语言构建企业级应用。 16. **第17章：WebSockets和JSON-P** - 最后，介绍了WebSocket协议和JSON-P（JSON with Padding），如何利用这些技术实现实时通信和数据传输。这本书不仅适合初学者作为Java EE入门教程，也适合有经验的开发人员查阅特定技术的深入细节，是一本非常实用的参考书籍。

CHAPTER 1 ■ INTRODUCTION TO SERVLETS

4. Copy the web.xml file that is in the source’s recipe01_02 directory into the WEB-INF

directory you created.

5. Download the JavaMail API code from Oracle, and copy the mail.jar file from the

download into the WEB-INF/lib directory you created. This API will be used to send mail

in future recipes.

6. Set your CLASSPATH to include the mail.jar file you downloaded in step 5.

7. At the command prompt, change directories so that you are in the classes directory you

created in step 2. Compile each recipe with the command javac org\javaeerecipes\

chapter01\recipe1_x\*.java

, where x is equal to the recipe number.

8. Copy your SimpleServlet application directory to the /JAVA_DEV/Glassfish/

glassfish/domains/domain1/autodeploy

directory for GlassFish or the

/Tomcat/webapps directory for Tomcat.

Test the application by launching a browser and going to http://localhost:8080/SimpleServlet/servlet_name,

where servlet_name corresponds to the servlet name in each recipe. If using Tomcat, you may need to restart

the server in order for the application to deploy.

How It Works

To compile the sources, you can use your favorite Java IDE such as NetBeans or Eclipse, or you can use the command

line. For the purposes of this recipe, I will do just that. If you’re using the command line, you must ensure you are

using the javac command that is associated with the same Java release that you will be using to run your servlet

container. In this example, we will say that the location of the Java SE 7 installation is at the following path:

/Library/Java/JavaVirtualMachines/1.7.0.jdk/Contents/Home

This path may differ in your environment if you are using a different operating system and/or installation

location. To ensure you are using the Java runtime that is located at this path, set the JAVA_HOME environment variable

equal to this path. On OS X and *nix operating systems, you can set the environment variable by opening the terminal

and typing the following:

export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.7.0.jdk/Contents/Home

If you are using Windows, use the SET command within the command line to set up the JAVA_HOME

environment variable.

set JAVA_HOME=C:\your-java-se-path\

Next, compile your Java servlet sources, and be sure to include the javax.servlet-api.jar file that is packaged

with your servlet container (use servlet-api.jar for Tomcat) in your CLASSPATH. You can set the CLASSPATH by using

the –cp flag of the javac command. The following command should be executed at the command line from within the

same directory that contains the sources. In this case, the source file is named SimpleServlet.java.

javac -cp /path_to_jar/javax.servlet-api.jar SimpleServlet.java

CHAPTER 1 ■ INTRODUCTION TO SERVLETS

Next, package your application by creating a directory and naming it after your application. In this case, create a

directory and name it SimpleServlet. Within that directory, create another directory named WEB-INF. Traverse into

the WEB-INF directory, and create another directory named classes. Lastly, create directories within the classes

directory in order to replicate your Java servlet package structure. For this recipe, the SimpleServlet.java class

resides within the Java package org.javaeerecipes.chapter01.recipe01_02, so create a directory for each of

those packages within the classes directory. Create another directory within WEB-INF and name it lib; any JAR files

containing external libraries should be placed within the lib directory. In the end, your directory structure should

resemble the following:

SimpleServlet

|_WEB-INF

|_classes

|_org

|_javaeerecipes

|_chapter01

|_recipe01_02

|_lib

Place your web.xml deployment descriptor within the WEB-INF directory, and place the compiled

SimpleServlet.class file within the recipe01_02 directory. The entire contents of the SimpleServlet directory can

now be copied within the deployment directory for your application server container to deploy the application.

Restart the application server if using Tomcat, and visit the URL http://localhost:8080/SimpleServlet/SimpleServlet

to see the servlet in action.

1-4. Registering Servlets Without WEB-XML

Problem

Registering servlets in the web.xml file is cumbersome, and you want to deploy servlets without modifying web.xml at all.

Solution

Use the @WebServlet annotation to register the servlet, and omit the web.xml registration. This will alleviate the

need to modify the web.xml file each time a servlet is added to your application. The following adaptation of the

SimpleServlet class that was used in Recipe 1-2 includes the @WebServlet annotation and demonstrates its use:

package org.javaeerecipes.chapter01.recipe01_04;

import java.io.IOException;

import java.io.PrintWriter;

import javax.servlet.ServletException;

import javax.servlet.annotation.WebServlet;

import javax.servlet.http.HttpServlet;

import javax.servlet.http.HttpServletRequest;

import javax.servlet.http.HttpServletResponse;

CHAPTER 1 ■ INTRODUCTION TO SERVLETS

In the solution to this recipe, the @WebServlet annotation maps the servlet class named

SimpleServletNoDescriptor to the URL pattern of /SimpleServletNoDescriptor, and it also names the servlet

SimpleServletNoDescriptor.

@WebServlet(name="SimpleServletNoDescriptor", urlPatterns={"/SimpleServletNoDescriptor"})

The new @WebServlet can be used rather than altering the web.xml file to register each servlet in an application.

This provides ease of development and manageability. However, in some cases, it may make sense to continue using

the deployment descriptor for servlet registration, such as if you do not want to recompile sources when a URL pattern

changes. If you look at the web.xml listing in Recipe 1-2, you can see the following lines of XML, which map the servlet

to a given URL and provide a name for the servlet. These lines of XML perform essentially the same function as the

@WebServlet annotation in this recipe.

<servlet-name>SimpleServletNoDescriptor</servlet-name>

<servlet-class>org.javaeerecipes.chapter01.recipe01_04.SimpleServletNoDescriptor</servlet-class>

</servlet>

<servlet-mapping>

<servlet-name>SimpleServletNoDescriptor</servlet-name>

<url-pattern>/SimpleServletNoDescriptor</url-pattern>

</servlet-mapping>

1-5. Displaying Dynamic Content with a Servlet

Problem

You want to display some content to a web page that may change depending upon server-side activity or user input.

Solution

Define a field within your servlet to contain the dynamic content that is to be displayed. Post the dynamic content on

the page by appending the field containing it using the PrintWriter println method. The following example servlet

declares a Date field and updates it with the current Date each time the page is loaded:

package org.javaeerecipes.chapter01.recipe01_05;

import java.io.IOException;

import java.io.PrintWriter;

import java.util.Date;

import javax.servlet.ServletException;

import javax.servlet.annotation.WebServlet;

import javax.servlet.http.HttpServlet;

import javax.servlet.http.HttpServletRequest;

import javax.servlet.http.HttpServletResponse;

/**

* Recipe 1-5: Displaying Dynamic Content with a Servlet

* @author juneau

剩余735页未读，继续阅读

natthapnog

粉丝: 1
资源: 6

2013年Apress《Java EE 7 Recipes》精华指南

Apress.Pro.Java.EE.Spring.Patterns.Aug.2008.rar

Apress.Beginning.Java.EE.7.2013

Apress.Introducing.Java.EE.7.Jul.2013.epub 完整版本

Apress.Java.7.Recipes.A.Problem-Solution.Approach.2011

Apress.Beginning.Java.EE.6.with.GlassFish.3.2nd.Edition

Apress.Begining EJB3 Java EE 7 Edition.2013

Apress.Pro.CDI.2.in.Java.EE.8.pdf

Apress.Windows.Phone.8.Recipes.Sep.2013

Apress.Entity.Framework.6.Recipes.2nd.Edition.Nov.2013

Apress.ASP.NET.MVC.4.Recipes.Feb.2013

最新资源