This repository has been archived by the owner on Dec 24, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
Developement Guidelignes
Davide Di Ruscio edited this page Mar 21, 2018
·
1 revision
| SCAVA Repository Organisation |
| Guideline describing how the SCAVA code repository is organised and how to add a new component in this repository |
| How to name SCAVA components ? |
| Guideline describing naming constraints for a new scava component (component name / java namespace / maven artefact id and group id...) |
| How to name SCAVA REST services ? |
| This guideline provide naming rules for each REST services routes implemented by the SCAVA platform. |
| How to manage Licensing ? |
| Guideline describing licensing requirements for SCAVA components. |
Each implemented REST services must be documented : REST API DOCUMENTATION
| How to configure the SCAVA Gateway in order to integrate a new REST service ? |
| Customers access SCAVA services through the SCAVA API Gateway. This guideline present how to configure the API Gateway to integrate new remote service provider. |
| How to consume a SCAVA REST services ? |
| This guideline is dedicated to clients which would like to used SCAVA REST Services.It adress authentication issues |
| How to implement Restlet services ? |
| Guideline which describe how to integrate and implement a REST service in SCAVA platform using the RESTLET framework. |
| How to access MongoDB database using PONGO ? |
| Guideline which describe how to the access to MongoDB database using the PONGO framework. |
| How to extend the SCAVA data model ? |
| Guideline which describe ways to extend the SCAVA Data Model, stored in a MongoDb database and based on the PONGO framework |
| How to integrate OSGI service plugin in SCAVA Architecture? |
| Todo |
| How to communicate between OSGI plugin using JMS ? |
| Todo |