Table 7-1. Design Directive Pointers
Spring Java EE Pattern
Remote dispatcher servlet
Web Service Broker
Data access object
Data Access Object
Once the design is in place, the next step is to start the development. Before you get
started, though, it's imperative that you set up the team development environment. For
the example OMS, I decided to use Blazon ezJEE 1.0.0, which is based on the Eclipse
Ganymede release. It is a comprehensive agile Java EE development environment and
comes bundled with all the essential plug-ins, including support for the Spring Frame-
work. If you are familiar with the Eclipse IDE, then getting started with Blazon ezJEE will
be a breeze. You can get Blazon ezJEE by following the download link at http://www.
Once you are done with the download, go through the quick-start guide to get started
with this IDE. I will use Apache Maven (included in Blazon ezJEE) to build and deploy the
web application artifacts. Maven is a useful tool for agile project development. It makes it
easy to develop, build, and deploy projects in a very flexible and modular way. It pro-
motes test-driven development by directly including unit test runs in the build process.
ous integration. In the next few sections, I will explain how you can use Blazon ezJEE to
set up the different projects required for the OMS application in the workspace.
Setting Up the Workspace
When you launch Blazon ezJEE for the first time, it will prompt you to select a workspace.
Simply, a workspace is a folder in which you will keep your other Eclipse project directo-
ries. Because I am developing this OMS on the Windows platform, I will supply the fully
qualified folder name as c:\omsworkspace , as shown in Figure 7-6.