By Antonio Goncalves
Read Online or Download Beginning Java EE 6 Platform with GlassFish 3, Second Edition PDF
Best economy books
This book assumes transformation of former socialist nations of Europe to a industry financial system to be a political idea, having a commence and an finish. Transformation is analyzed from the point of view of the top (EU membership), and never of the inherited burdens from the socialist procedure. also, the authors examine the result of transformation and its skill to enhance social criteria, source of revenue, and progress.
Delivering an intensive and updated evaluation of the total diversity of gynaecological cancers, Gynaecological Oncology is a concise advent, relatively necessary for trainees practicing postgraduate examinations. the 1st part contains introductory chapters on epidemiology, screening and prevention, imaging, pathology, surgical procedure, radiation treatment, chemotherapy, and palliation.
Extra resources for Beginning Java EE 6 Platform with GlassFish 3, Second Edition
Starting with Java EE 6, web applications can also contain EJBs Lite (more on that in Chapter 6). 5 CHAPTER 1 ■ JAVA EE 6 AT A GLANCE • Enterprise applications (made of Enterprise Java Beans, Java Message Service, Java Transaction API, asynchronous calls, timer service, RMI/IIOP) are executed in an EJB container. EJBs are container-managed components for processing transactional business logic. They can be accessed locally and remotely through RMI (or HTTP for SOAP and RESTful web services). Containers The Java EE infrastructure is partitioned into logical domains called containers (see Figure 1-2).
Specifications don’t cover all the details, and implementations end up providing nonportable solutions. That’s what happened with JNDI names, for example. If you deployed an EJB to GlassFish, JBoss, or WebLogic, the JNDI name was different because it wasn’t part of the specification, so you had to change your code depending on the application server you used. That particular problem has now been fixed, because Java EE 6 specifies a syntax for JNDI names that is the same across application servers (see Chapter 7).
Project Modularity To address project modularity, Maven provides a mechanism based on modules. Each module is a Maven project in its own right. Maven is able to build a project with different modules by calculating the dependencies they have between them (see Figure 1-11). To facilitate reusing common parameters, POM descriptors can inherit from parent POM projects. 24 CHAPTER 1 ■ JAVA EE 6 AT A GLANCE Figure 1-11. A project and its modules Plug-ins and Life Cycle Maven uses a life cycle made of several phases (see Figure 1-12): it cleans the resources, validates the project, generates any needed sources, compiles Java classes, runs test classes, packages the project, and installs it to the local repository.