The PROJECT collection houses all published (i.e. usable) projects. While design artifact are spread over multiple collections, each PROJECT entry brings together all the artifacts relevant to a given project in a single document.
{
"_id" : "",
"wid" : "",
"version" : 0,
"wip" : 0,
"name" : "",
"connectors" : [],
"aggregates" : [],
"webservices" : [],
"notifications" : []
}
Attribute |
Value |
Note |
_id |
A unique identifier for the published project |
Not the same as the design project _id |
wid |
The _id of the corresponding design project (PROJECT_WIP) |
|
version |
The major version of the published project |
The values of version and wip the design project was on before publishing. |
wip |
The minor version of the published project |
|
name |
The name of the published project |
The same as the name of the design project or a variation denoting a Webservice-specific publishing (*). |
connectors |
The list of connectors in the project in the published form of CONNECTOR |
|
aggregates |
The list of aggregates defined in the project, in the published form of AGGREGATE |
|
webservices |
The list of webservices defined in the project, in the published form of WEBSERVICE |
|
notifications |
The list of notification routes defined in the project, in the published form of NOTIFICATIONS |
|
(*) Each time a Webservice WAR is generated, a snapshot of the Project it belongs to is saved in the PROJECT collection.
This is due to the fact that the generated WAR contains hardcoded resources referencing project artifacts. These can change in the base PROJECT entry when a new version is published, so a snapshot is kept so that the Webservice does risk becoming inoperative.