Chapter 14. Enterprise Java

 

This chapter covers:

  • 14.1 Evolving the diary application
  • 14.2 Making an Enterprise application
  • 14.3 Creating the beans
  • 14.4 Extending the web application
  • 14.5 Building the Enterprise application
  • 14.6 Deploying to the application server
  • 14.7 Server-side testing with Apache Cactus
  • 14.8 Summary

It’s time to move our application up a notch. We’re going to make it an Enterprise application. One way to do this is to use Java Enterprise Edition (Java EE), the product formerly known as Java 2 Enterprise Edition (J2EE). According to Sun’s web site (http://java.sun.com/javaee/), “Java EE provides web services, component model, management, and communications APIs that make it the industry standard for implementing Enterprise-class service-oriented architecture (SOA) and Web 2.0 applications.”

What that means is that the Java EE API provides all the APIs needed to make Java classes persistent to a database, and for the outside world to talk to the application over HTTP, CORBA, or the Web Service protocols. It doesn’t provide implementations; Java EE applications work properly only inside an application server. This makes development and testing harder than it is for anything else we’ve covered so far.

14.1. Evolving the diary application

14.2. Making an Enterprise application

14.3. Creating the beans

14.4. Extending the web application

14.5. Building the Enterprise application

14.6. Deploying to the application server

14.7. Server-side testing with Apache Cactus

14.8. Summary