Make your application call my application, part 2nd: James Application

Continue with your unfinished studies in part 1th, in part 1th, you learned how to develop message-driven beans (MDB), entity beans, and container-managed persistence (CMP), and how to deploy and test these components in Apache Geronimo. This is the 2nd part of a three-part series that shows you the overall architecture of Java Apache Mail Enterprise Server (also known as Apache James). You'll learn how to build, deploy, and test your e-mail applications (Mailet and Matcher) and how to deploy this application in your Apache James e-mail server.

Before you start

This series of tutorials is geared toward learning how to use various Java EE components-including MDB and Java 2 platform,enterprise Edition (EE) Connector Architecture (JCA) resource adapters-building an integrated Java™platform of the solution, Enterprise Edition (Java EE) programmer. This tutorial assumes that you are familiar with basic Java and Java EE concepts such as EJB, Java message Service (JMS), MDB, and Unified Modeling Language (UML) diagrams.

About this series

In this three-part series, you'll build a sample application that understands how to integrate different Java EE components to develop complex applications.

You can download the sample application for this article, which demonstrates that the data for e-mail in Apache James is flowing to the Apache Geronimo Application server via a JCA resource adapter, MDB, EJB.

Part 1th of this series describes how to develop MDB, entity beans, and container-managed persistence (CMP), and how to deploy and test these components in Apache Geronimo.

This issue is the 2nd part of a series of tutorials that explains how to create an e-mail application (Mailet and Matcher) and deploy it in the Apache James e-mail server.

The 3rd part links the entire application together. You will learn to develop, deploy, and test the JCA resource adapter for the Apache James e-mail server, which will interact with James and Geronimo through an MDB.

About this tutorial

In part 1th, you built the MDB and entity beans to create a purchase order item in the Apache Derby database. In this tutorial, you will learn about the overall architecture of Apache James and build an e-mail application that handles incoming e-mail messages.

Prerequisite

This tutorial does not ask you to have any prior knowledge of Apache James or JavaMail, but I want you to understand how e-mail works.

System Requirements

To complete this tutorial, you need the following tools:

Java EE Application Server provided by Apache Geronimo--apache

Apache James 2.2-—— Java-based simple Mail Transfer Protocol (SMTP), Post Office Protocol version 3 (POP3), and network News Tran Sfer Protocol (NNTP) news server

Apache Derby Database-open source, lightweight database, embedded in Geronimo, no need to install independently

Java 1.4.2 provided by Sun Microsystems

Sample source file

To get started, download part2.source.zip (see the Downloads section), which includes the source files, Mailet binaries, and. bat files that are mentioned in this tutorial. The following is a detailed list of the components of the Part2.source.zip file:

-Deploy (Po-mailet.jar, containing Mailet and Matcher)

-Lib (Tester.jar)

-SRC (Mailet, matcher, and test client Java files)

-Deploy.cmd

-Undeploy.cmd

-Runsendemail.cmd

-Runreademail.cmd

Apache james--Overview

To continue developing the sample application, you need a good understanding of the Apache James server. This section briefly describes the James server and its components.