FESA3 Database Workflow - Issues to consider

The integration of the FESA3 database may affect the FESA development workflow known so far. If FESA software is supposed to be accessible via JAPC (Java applications) the FESA designs must be exported to the database. The following issues should be considered when using the database:
  • before a deploy-unit can be exported to the database the included class(es) must be exported first
  • before explicitly exporting an instance document the class and the deploy-unit must be in the database
  • FESA documents with certain versions can only be inserted once into the database. The class / deploy-unit version must be increased for classes / deploy-units: when the design document has already been exported to the database in a certain version

-- SolveighMatthies - 17 Mar 2015
Topic revision: r3 - 08 Sep 2015, SolveighMatthies
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback