Creating carbon projects

When we develop a WSO2 Enterprise Integrator application, we can create different types of projects depending on the functionality required. These projects are called carbon projects, and there are several kinds of projects depending on the functionality needed.

As you may remember from Chapter 1, Getting Started with SOA and WSO2, WSO2 Enterprise Integrator is a bundle made up of previous individual products. Hence, we will have to create different kinds of projects depending on the built-in product in which we are implementing each part of our application functionality. Thus, we have different projects for the Enterprise Service Bus (ESB), Data Services Server (DSS), or Business Process Server (BPS) built-in components.

Focusing on the scope of the book, we will make use of the following:

• ESBConfig Project: This project contains all artifacts related to the functionality developed in the ESB.
• Registry Resource Project: This project will be used to add resources such as XSL transformations, WSLD files, and XSD files to the EI registry. Some of the artifacts used to develop our application require complementary files that must be stored in the EI registry.
• Data Service Project: In this kind of project, we add the data services required in our application.
• Composite Application Project: This project generates the deployable artifact of our application. It detects the existing artifacts in the projects within the workspace and allows us to select which ones will be packaged in a composite application that will be deployed in WSO2EI.
• ESB Solution Project: This project is not a real project; rather, it can be considered as a wizard, as it can make a developer's life easier. It allows us to create the most common projects needed in a service development using just one wizard.

All these projects use Maven technology, so we will find the mandatory pom.xml file required in these types of projects in all of them.