JBoss.orgCommunity Documentation
It is necessary to create a JAIN SLEE project before JAIN SLEE components may be created. This can be done from the workbench by selecting
→ → as illustrated in the following figure.
This will create a New Project dialog as shown below. From this dialog expand JAIN SLEE, then select the revealed JAIN SLEE Project. Click to proceed to chosing a name and location for the new project.
Give the project a name and if desired specify a non-default location. For the majority of people the default location will be fine; this is the current workspace. The following image shows a project with the name of 'MobicentsDemoProject' in the default location. Click
to proceed to module selection or to go with default (SBBs and Deployable Unit).
Choose the desired project modules to be created, from the list, as shown below. The correct Maven modules will be created according to the selection, as well as the Deployable Unit descriptor. You can also opt for using the Mobicents JAIN SLEE 1.1 specific extensions. You can find more information about these extensions on the Mobicents JAIN SLEE User Guide.
Click on and the project with all the modules will be created in the selected location.
The following image depicts a workspace with a newly created JAIN SLEE project with the project folder, "MobicentsDemoProject", expanded.
It is possible to manage (ie, add, modify and remove) modules once the project is created.
Adding a new module can be done from the workbench by right-clicking the Project element and selecting
→ as illustrated in the following figure, for a Resource Adaptor Type.
This will create a New Module dialog as shown below. From this dialog it's possible to name the new module and select from which other existing modules this one will depend on (Dependency) and which ones will depend on the new one (Dependant).
The deployable unit (du) module must always be selected as dependant if the new module should be included in the maven generated Deployable Unit.
The module name will always be suffixed with "-<component_type>" (eg: Using Name "custom" in example will result in "custom-ratype" module) so, avoid including it in the name.
Click on and the new module will be created and dependencies in other modules will be updated to include it.
Editing a new module can be done from the workbench by right-clicking the Project element and selecting
→ as illustrated in the following figure, for a Resource Adaptor Type.
This will present a dialog similar to the New Module dialog. From this dialog it's possible to modify from which other existing modules this one will depend on (Dependency) and which ones will depend on this one (Dependant).
The deployable unit (du) module must always be selected as dependant if the new module should be included in the maven generated Deployable Unit.
When done with the desired changes, click on and the affected modules will be updated.
Removing an existing module can be done from the workbench by right-clicking the Project element and selecting
→ as illustrated in the following figure, for a Resource Adaptor Type.
This will present a confirmation dialog to confirm the deletion of the module.
Deleting a module is an irreversible operation, so it should be used carefully.
Click on to delete the module and update references in other modules. Clicking cancels the operation without performing any action.
Maven dependencies for each module can be added or removed using EclipSLEE, with no need to use third-party maven plugins.
Adding a new maven dependency can be done from the workbench by right-clicking the desired module pom file and selecting
as illustrated in the following figure.
This will create a New Maven Dependency dialog as shown below. From this dialog it's possible to define the dependency Group ID, Artifact ID and Version, as well as the scope with which the dependency should be added (defaulting to "compile"). The Add to classpath? option adds the new maven dependency to the project classpath, considering "M2_REPO" variable is set.
Under Eclipse preferences, go to Name as M2_REPO
and Path indicating the path to your Maven local repository (usually located under <user-home>/.m2/repository). Click OK to save and close the dialog, and OK again to close the preferences window.
Click on and the new dependency will be added to the module's pom file and, if selected, the classpath updated with the new entry.
Removing a Maven dependency can be done from the workbench by right-clicking the desired module pom file and selecting
→ as illustrated in the following figure.
This will present a confirmation dialog to confirm the removal of the maven dependency.
Click on to remove the maven dependency from the module and, if needed, update the classpath. Clicking cancels the operation without performing any action.