Java Reference
In-Depth Information
Summary
In this chapter, we went through a critical part of enterprise systems: integration testing.
Historically, one main downside of Java EE is its testability, but Arquillian has really
solved this issue to a great extent.
Used as an extension to the JUnit framework, Arquillian excels in checking the integration
layer that exposes the business logic in an enterprise Java application.
Arquillian hooks into your testing framework to manage the container's life cycle. It also
bundles the
test
class into a deployable archive with dependent classes and resources.
This is the last chapter covering basic Java EE and WildFly features. We started with a few
session beans, and ended up with web sockets, an asynchronous messaging system, REST-
ful API, and even a little bit of JavaScript. During the course of this topic, we saw how the
newest edition of Java EE provided us with tools to create modern and scalable applica-
tions. The platform's goal is to help the developer to focus on the business logic. This
means removing the boilerplate code through the whole application stack from the backend
to the view layer. In most areas, we only covered the most important features of the mul-
tiple technologies provided by Java EE. There is still plenty to explore!
In the appendix, we will learn a few things about the JBoss Forge tool, which can greatly
increase the productivity when working with Java EE.
