Skip to main content

Repository map

Openflexo is not a single repository: the infrastructure is made of independent repositories, each with its own history and its own version. They are listed below, grouped by role.

Layering is strict, bottom-up: Connie, then Pamela, then Gina and Diana, then the core (openflexo-core), the user interface, the technology adapters, the server and finally the applications. A layer never depends on a higher one, and a technology adapter never depends on another one. See Set up your workspace to check them out and build them together, and Component versions for which version of each goes with a release.

Core and frameworks

RepositoryDescriptionStatus
openflexo-buildpluginGradle build plugin and version configuration shared by every repositoryActive
connieExpression language and binding frameworkActive
dianaDiagramming and 2D drawing frameworkActive
ginaGeneric user-interface framework: widgets, panels, inspectorsActive
pamelaModeling framework: annotated interfaces woven into stateful model objectsActive
pamela-editorEditor for Pamela metamodelsActive
openflexo-utilsShared utility classesActive
openflexo-coreModel federation engine and FML, the Flexo Modeling LanguageActive
openflexo-uiShared user-interface components of the Openflexo applicationsActive
modelersBPMN, UML, statecharts and OWL modelersActive
openflexo-integration-testsRegression tests and example federation use casesActive
openflexo-packagingAssembles modules and technology adapters into downloadable packagesActive
pimcaDomain-specific systems modeling language for cyber threat analysisResearch prototype
ctaCyber Threat Application, built on Pimca (see Research)Research prototype
formodFormose application: the B technology adapter, its module and its testsResearch prototype

Technology adapters

RepositoryDescriptionStatus
openflexo-technology-adaptersHistorical container of technology adapters, now holding only the xx-ta templateLegacy
openflexo-diagramOpenflexo's native diagramming technologyStabilised
openflexo-docxMicrosoft Word documents (.doc, .docx)Stabilised
openflexo-emfEMF-based metamodels and modelsStabilised
openflexo-ginaGINA user-interface components, as a federated resourceRetired
openflexo-httpGeneric HTTP endpointsRetired
openflexo-restREST web servicesMigration in progress
openflexo-javaJava source codeLimited support
openflexo-jdbcRelational databases via JDBCMigration in progress
openflexo-kafkaApache Kafka streamsLimited support
openflexo-owlOWL2 ontologiesStabilised
openflexo-opc-uaOPC-UA industrial automation serversActive development
openflexo-capellaCapella / Arcadia system modelsActive development
openflexo-obp2Connector for the OBP2 toolRetired
openflexo-odtOpenDocument Text documents (.odt)Not yet classified
openflexo-oslcOSLC-linked resourcesRetired
openflexo-pdfPDF documentsLimited support
openflexo-pptxMicrosoft PowerPoint presentations (.ppt, .pptx)Migration in progress
openflexo-rhapsodyIBM Rational Rhapsody modelsRetired
openflexo-xlsxMicrosoft Excel spreadsheets (.xls, .xlsx)Stabilised
openflexo-xmlXML documents, typed against an XSD or freely structuredStabilised
openflexo-jsonJSON documentsActive development
openflexo-markdownMarkdown documentsLimited support
openflexo-mcpModel Context Protocol serversActive development
openflexo-csvCSV filesActive development

Server

RepositoryDescriptionStatus
openflexo-serverHTTP server exposing the Openflexo infrastructure through a REST APIActive

Application modules

RepositoryDescriptionStatus
openflexo-modulesTemplate (xxxmodule) for building a new application moduleActive
openflexo-modellerOpenflexo Modeller application: define and run model federationsActive
free-modelling-editorFreeModellingEditor application: build free graphical modelsActive
enterprise-architecture-editorEnterprise Architecture editor applicationActive

Statuses

Technology adapters follow the review made by the architecture board on 2026-04-03:

  • Stabilised: complete and stable.
  • Migration in progress: being migrated to the current architecture.
  • Active development: new adapter, still being developed.
  • Limited support: still available, with limited maintenance.
  • Retired: no longer maintained nor shipped.

Other repositories are Active (maintained, part of the current platform), a Research prototype (built for a research project), Legacy (kept for history) or Retired.