fva-net/rexs-api-java

Purpose and Modules

REXS-API is a Java 17 library for reading, writing, transforming, validating, and upgrading REXS engineering-model files. Maven root pom.xml coordinates two deliverables: reusable API library api/pom.xml and command-line application cli/pom.xml.

Public Entry Points

Library consumers primarily enter through file-format abstractions and model APIs:

• api/src/main/java/info/rexs/io/RexsFileReader.java

• api/src/main/java/info/rexs/io/RexsFileWriter.java

• api/src/main/java/info/rexs/io/RexsFileUpgrader.java

The executable entry point is cli/src/main/java/info/rexs/cli/Application.java; it exposes conversion and validation workflows over the API.

Canonical Domain Model

The central in-memory boundary is the REXS model: models contain components, attributes, relations, submodels, and load spectra. Typed value classes represent scalar, array, matrix, and Base64-encoded attribute payloads.

• api/src/main/java/info/rexs/model/IRexsModel.java

• api/src/main/java/info/rexs/model/RexsModel.java

• api/src/main/java/info/rexs/model/RexsComponent.java

This domain representation decouples callers from XML, JSON, and ZIP serialization details.

Format I/O and Transformation

Reader/writer implementations ingest or emit the canonical model in XML, JSON, or ZIP-packaged forms. Abstract I/O bases and Resource implementations establish the file/byte-array input-output boundary. Transformers map between the domain model and serialization-specific representations.

• api/src/main/java/info/rexs/io/xml/RexsXmlFileReader.java

• api/src/main/java/info/rexs/io/json/RexsJsonFileWriter.java

• api/src/main/java/info/rexs/io/zip/RexsZipFileReader.java

• api/src/main/java/info/rexs/model/transformer/RexsModelXmlTransformer.java

Typical flow: resource/file → format reader → format-specific representation/transformer → IRexsModel; writing reverses this path.

Versioned Schema Resolution

Schema registries and resolvers provide version-aware metadata for REXS attributes, component types, relations, units, and value types. Embedded schema XML files are runtime resources, not remote services.

• api/src/main/java/info/rexs/schema/RexsSchemaRegistry.java

• api/src/main/java/info/rexs/schema/RexsSchemaResolver.java

• api/src/main/resources/info/rexs/schema/rexs_schema_2.0.0.xml

Constants under schema/constants provide strongly typed identifiers and standard vocabulary; schema resolution is the key boundary between generic model objects and a particular REXS version.

Validation Pipeline

Validation operates at file, model, component, relation, and attribute levels, returning structured results/messages. Standard validators enforce REXS rules; modelling-guideline validators add quasistatic-specific checks.

• api/src/main/java/info/rexs/validation/DefaultRexsFileValidator.java

• api/src/main/java/info/rexs/validation/DefaultRexsModelValidator.java

• api/src/main/java/info/rexs/validation/RexsStandardFileValidator.java

The CLI validation command invokes this layer rather than embedding independent validation rules.

Upgrade and CLI Orchestration

Upgrade logic resolves chained version migrations, applies model upgraders, and uses embedded changelog resources to move files from REXS 1.0 through 2.0. CLI conversion combines read, optional upgrade/version targeting, and write; validation reads then validates.

• api/src/main/java/info/rexs/upgrade/RexsUpgrader.java

• api/src/main/java/info/rexs/upgrade/upgraders/UpgradeResolver.java

• api/src/main/resources/info/rexs/upgrade/upgraders/changelog/rexs_changelog_1.7_to_2.0.0.xml

• cli/src/main/java/info/rexs/cli/convert/ConvertCommandServiceImpl.java

• cli/src/main/java/info/rexs/cli/validate/ValidateCommandServiceImpl.java

CI/release automation is provided by GitHub Actions in .github/workflows/build.yml and .github/workflows/release.yml; no deployed infrastructure or external runtime service is indicated.