12.07.2015 Views

Beginning Java EE 6 with GlassFish 3, Second Edition

Beginning Java EE 6 with GlassFish 3, Second Edition

Beginning Java EE 6 with GlassFish 3, Second Edition

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CHAPTER 1 ■ JAVA <strong>EE</strong> 6 AT A GLANCE<strong>Java</strong> <strong>EE</strong> 6 is an important milestone. Not only does it follow the steps of <strong>Java</strong> <strong>EE</strong> 5 by focusing on aneasier development model, it also adds new specifications and brings profiles and pruning to make itlighter. The release of <strong>Java</strong> <strong>EE</strong> 6 coincides closely <strong>with</strong> the tenth anniversary of the enterprise platform. Itcombines the advantages of the <strong>Java</strong> language <strong>with</strong> experience gained over the last ten years. Moreover,it profits from the dynamism of open source communities as well as the rigor of the JCP. Today <strong>Java</strong> <strong>EE</strong> isa well-documented platform <strong>with</strong> experienced developers, a large community, and many deployedapplications running on companies’ servers. <strong>Java</strong> <strong>EE</strong> is a suite of APIs to build standard componentbasedmultitier applications. These components are deployed in different containers offering a series ofservices.A Bit of HistoryTen years is a good time to look back at the evolution of <strong>Java</strong> <strong>EE</strong> (see Figure 1-1), which was formerlycalled J2<strong>EE</strong>. J2<strong>EE</strong> 1.2, first developed by Sun, was released in 1999 as an umbrella specificationcontaining ten <strong>Java</strong> Specification Requests (JSRs). At that time people were talking about CORBA, soJ2<strong>EE</strong> 1.2 was created <strong>with</strong> distributed systems in mind. Enterprise <strong>Java</strong> Beans (EJBs) were introduced<strong>with</strong> support for remote stateful and stateless service objects, and optional support for persistent objects(entity beans). They were built on a transactional and distributed component model using RMI-IIOP(Remote Method Invocation–Internet Inter-ORB Protocol) as the underlying protocol. The web tier hadservlets and <strong>Java</strong>Server Pages (JSPs), and JMS was used for sending messages.Figure 1-1. History of J2<strong>EE</strong>/<strong>Java</strong> <strong>EE</strong>2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!