Understanding Project Dependencies

A dependency is a situation where a project requires some other component to build or deploy correctly. This topic describes how to set up and manage dependencies between components in order to assemble a working enterprise application. For the most part, these dependencies are created automatically for you, and the information in this topic is only required if you wish to modify or delete dependencies.

The assembly point for an enterprise application is an enterprise application (EAR) project. Other projects are added to the EAR project as necessary:

and shared projects are added to the EAR and made available to the existing web projects:

The usual structure looks something like this where all projects are connected to the application (as shown by solid lines in the digaram below), and the shared projects are also made available to the web projects (the thick dotted lines in the diagram):

To build an enterprise application correctly, all shared projects must be correctly connected to the web projects that depend on the shared code.

To deploy an enterprise application correctly, all web services, dynamic web projects (web applications), utility and EJB projects must be added to the EAR project. All projects in an EAR are deployed together, whether to a server or for archiving to an EAR file.

Dependencies on Other Code Sources

In addition to project dependencies, projects may also require:

Still need help? Post a question on the Workshop newsgroup.