Goncalves - Beginning Java EE 7
Here you can read online Goncalves - Beginning Java EE 7 full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. City: Berkeley;CA;New York;Place of publication not identified, year: 2013, publisher: APress, Distributed by Springer Science+Business Media, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
Beginning Java EE 7: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "Beginning Java EE 7" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Contents at a Glance -- Contents -- Foreword -- About the Author -- About the Technical Reviewer -- Acknowledgments -- Introduction -- Chapter 1: Java EE 7 at a Glance -- Understanding Java EE -- Architecture -- Components -- Containers -- Services -- Network Protocols -- Packaging -- Annotations and Deployment Descriptors -- Standards -- JCP -- Portable -- Programming Model -- Java Standard Edition 7 -- String Case -- Diamond -- Try-with-Resources -- Multicatch Exception -- NIO.2 -- Java EE Specifications Overview;Java Enterprise Edition (Java EE) continues to be one of the leading Java technologies and platforms. Beginning Java EE 7 is the first tutorial book on Java EE 7. Step by step and easy to follow, this book describes many of the Java EE 7 specifications and reference implementations, and shows them in action using practical examples. This definitive book also uses the newest version of GlassFish to deploy and administer the code examples. Written by an expert member of the Java EE specification request and review board in the Java Community Process (JCP), this book contains the best information possible, from an experts perspective on enterprise Java technologies.
Goncalves: author's other books
Who wrote Beginning Java EE 7? Find out the surname, the name of the author of the book and a list of all author's works by series.
Goncalves
Herbert Schildt
Gupta
David Flanagan
Cay S. Horstmann
Arun Gupta
David R. Heffelfinger
James Gosling
Arun Gupta
Antonio Goncalves
Jonathan Wetherbee
Beginning Java EE 7 — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Beginning Java EE 7" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Light
Font size:
↓
↑
Reset
Interval:
↓
↑
Bookmark:
Make
Antonio Goncalves Beginning Java EE 7 10.1007/978-1-4302-4627-5_1
Antonio Goncalves 2013
1. Java EE 7 at a Glance
Antonio Goncalves 1
(1)
Paris, France
Abstract
Enterprises today live in a globally competitive world. They need applications to fulfill their business needs, which are getting more and more complex. In this age of globalization, companies are distributed over continents, they do business 24/7 over the Internet and across different countries, have several datacenters, and internationalized systems which have to deal with different currencies and time zonesall that while reducing their costs, lowering the response times of their services, storing business data on reliable and safe storage, and offering several mobile and web interfaces to their customers, employees, and suppliers.
Enterprises today live in a globally competitive world. They need applications to fulfill their business needs, which are getting more and more complex. In this age of globalization, companies are distributed over continents, they do business 24/7 over the Internet and across different countries, have several datacenters, and internationalized systems which have to deal with different currencies and time zonesall that while reducing their costs, lowering the response times of their services, storing business data on reliable and safe storage, and offering several mobile and web interfaces to their customers, employees, and suppliers.
Most companies have to combine these complex challenges with their existing enterprise information systems (EIS) at the same time developing business-to-business applications to communicate with partners or business-to-customer systems using mobile and geolocalized applications. It is also not rare for a company to have to coordinate in-house data stored in different locations, processed by multiple programming languages, and routed through different protocols. And, of course, it has to do this without losing money, which means preventing system crashes and being highly available, scalable, and secure. Enterprise applications have to face change and complexity, and be robust. Thats precisely why Java Enterprise Edition (Java EE) was created.
The first version of Java EE (originally known as J2EE) focused on the concerns that companies were facing back in 1999: distributed components. Since then, software applications have had to adapt to new technical solutions like SOAP or RESTful web services. The Java EE platform has evolved to respond to these technical needs by providing various ways of working through standard specifications. Throughout the years, Java EE has changed and became richer, simpler, easier to use, more portable, and more integrated.
In this chapter, Ill give you an overview of Java EE. After an introduction to its internal architecture, components, and services, Ill cover whats new in Java EE 7.
Understanding Java EE
When you want to handle collections of objects, you dont start by developing your own hashtable; you use the collection API (application programming interface ). Similarly, if you need a simple Web application or a transactional, secure, interoperable, and distributed application, you dont want to develop all the low-level APIs: you use the Enterprise Edition of Java. Just as Java Standard Edition (Java SE) provides an API to handle collections, Java EE provides a standard way to handle transactions with Java Transaction API (JTA), messaging with Java Message Service (JMS), or persistence with Java Persistence API (JPA). Java EE is a set of specifications intended for enterprise applications. It can be seen as an extension of Java SE to facilitate the development of distributed, robust, powerful, and highly available applications.
Java EE 7 is an important milestone. Not only does it follow in the footsteps of Java EE 6 by focusing on an easier development model, but it also adds new specifications, as well as adding new functionalities to existing ones. Moreover, Context and Dependency Injection (CDI) is becoming the integration point between all these new specifications. The release of Java EE 7 coincides closely with the 13th anniversary of the enterprise platform. It combines the advantages of the Java language with experience gained over the last 13 years. Java EE profits from the dynamism of open source communities as well as the rigor of the JCP (Java Community Process) standardization process. Today Java EE is a well-documented platform with experienced developers, a large community, and many deployed applications running on companies servers. Java EE is a suite of APIs that can be used to build standard component-based multitier applications. These components are deployed in different containers offering a series of services.
Architecture
Java EE is a set of specifications implemented by different containers. Containers are Java EE runtime environments that provide certain services to the components they host such as life-cycle management, dependency injection, concurrency, and so on. These components use well-defined contracts to communicate with the Java EE infrastructure and with the other components. They need to be packaged in a standard way (following a defined directory structure that can be compressed into archive files) before being deployed. Java EE is a superset of the Java SE platform, which means Java SE APIs can be used by any Java EE components.
Figure shows the logical relationships between containers. The arrows represent the protocols used by one container to access another. For example, the web container hosts servlets, which can access EJBs through RMI-IIOP. 
Figure 1-1.
Standard Java EE containers
Components
The Java EE runtime environment defines four types of components that an implementation must support:
- Applets are GUI (graphic user interface) applications that are executed in a web browser. They use the rich Swing API to provide powerful user interfaces.
- Applications are programs that are executed on a client. They are typically GUIs or batch-processing programs that have access to all the facilities of the Java EE middle tier.
- Web applications (made of servlets, servlet filters, web event listeners, JSP and JSF pages) are executed in a web container and respond to HTTP requests from web clients. Servlets also support SOAP and RESTful web service endpoints. Web applications can also contain EJBs Lite (more on that in ).
- 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 ). Each container has a specific role, supports a set of APIs, and offers services to components (security, database access, transaction handling, naming directory, resource injection). Containers hide technical complexity and enhance portability. Depending on the kind of application you want to build, you will have to understand the capabilities and constraints of each container in order to use one or more. For example, if you need to develop a web application, you will develop a JSF tier with an EJB Lite tier and deploy them into a web container. But if you want a web application to invoke a business tier remotely and use messaging and asynchronous calls, you will need both the web and EJB containers. Java EE has four different containers:
Light
Font size:
↓
↑
Reset
Interval:
↓
↑
Bookmark:
Make
Similar books «Beginning Java EE 7»
Look at similar books to Beginning Java EE 7. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Herbert Schildt
Gupta
David Flanagan
Cay S. Horstmann
Arun Gupta
David R. Heffelfinger
James Gosling
Arun Gupta
Antonio Goncalves
Jonathan Wetherbee
Reviews about «Beginning Java EE 7»
Discussion, reviews of the book Beginning Java EE 7 and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.