fva-net/maxs-logger-java

Purpose and packaging

maxs-logger-java is a Java 17/Maven library, not an application: consuming software uses it to produce MAXS .maxs XML log files. Its public operational entry point is src/main/java/de/fva_net/maxs/logger/MaxsLogger.java; routine implementations integrate through src/main/java/de/fva_net/maxs/logger/MaxsLoggableRoutine.java. Maven packaging, dependencies, and release coordinates are defined in pom.xml.

Logging façade and control boundary

MaxsLogger accepts logging requests, associates them with a loggable routine/context, and orchestrates validation plus XML notification output. MaxsLoggableRoutine is the principal extension boundary for REXS/model-side code: callers implement or supply routine metadata rather than coupling their domain models directly to XML persistence. Relevant paths:

• src/main/java/de/fva_net/maxs/logger/MaxsLogger.java

• src/main/java/de/fva_net/maxs/logger/MaxsLoggableRoutine.java

Message classification

MaxsMessageType defines the supported severity/category vocabulary (such as INFO, WARNING, and ERROR) used when creating notifications. This separates caller intent from the serialized XML representation and gives the logger a constrained message-type contract.

• src/main/java/de/fva_net/maxs/logger/MaxsMessageType.java

XML notification domain model

The logger serializes through dedicated XML-oriented DTOs rather than exposing file-format details to callers. Notification represents one logged event; Item represents associated attributes/items; KernelNotifications acts as the document-level notification collection/root. These types carry the required and non-zero attribute validation implied by the MAXS format.

• src/main/java/de/fva_net/maxs/logger/xml/Notification.java

• src/main/java/de/fva_net/maxs/logger/xml/Item.java

• src/main/java/de/fva_net/maxs/logger/xml/KernelNotifications.java

Primary flow and persistence

A consumer invokes MaxsLogger with a severity, message, routine/context, and optional structured attributes. The logger maps the request into Notification and Item objects, validates format-required fields, aggregates notifications in KernelNotifications, then writes an XML document to a .maxs file. The key boundary is between the public logger API and the XML schema model: callers work with logging semantics, while XML classes own serialized structure.

• src/main/java/de/fva_net/maxs/logger/MaxsLogger.java

• src/main/java/de/fva_net/maxs/logger/xml/KernelNotifications.java

• src/main/java/de/fva_net/maxs/logger/xml/Notification.java

Runtime, integration, and delivery

Runtime requirements are a Java 17+ JVM and local filesystem access for .maxs output. The library is built and published through Maven; GitHub Actions provide build and release automation under .github/workflows/. Its material external integration is REXS model-component usage through the routine abstraction, rather than a network service or server runtime.

• pom.xml

• .github/workflows/build.yml

• .github/workflows/release.yml