...
![]() Table of Contents |
|
|
Source tree <= 1.2.X
Up to 1.2.X, the effective source tree (e.g. excluding utility modules providing the standalone distribution, .deb artifacts, installer, ...) is organized into four main modules:
...
The nice part about this is that generated projects can easily override any single file from the official Syncope Maven artifacts; the major drawbacks are that the whole Maven artifacts need to be downloaded, and that any single feature to be implemented must be thought as a "deviation" from the standard behavior; moreover, even if some features are not required in the specific project (Activiti workflow adapter, Camel integration, ...) the related dependencies are still to be carried over, because they are part of the official artifacts.
Source tree >= 2_0_X
Starting with 2.0.0, the modules were re-organized according to the following package diagram (where packages are Maven modules, actually):
...
![]() Info |
| Even if not likely at the moment, one can think to provide an alternative, LDAP or MyBatis based, implementation for syncope-core-persistence-api. |
The upgraded archetype
The upgraded archetype for 2.0.X is still generating the core and console sub-modules as web applications; differently from the past, however, such applications enlist as dependencies one or more Syncope JAR artifacts (no more WAR overlays).
Core
The following dependencies are set:
...
- syncope-ext-camel-rest-cxf
Provides implementation of additional REST interface methods
- syncope-ext-camel-provisioning
Camel-based implementation of syncope-provisioning-api
- syncope-ext-camel-persistence-jpa
OpenJPA extensions for managing additional persistence table
Console
The following dependency is set:
...
