Repository navigation
Releases
TIE 0.6.0
A file whose name matches the patterns of several layouts no longer blocks every run when one of those layouts has already processed it. Without overlapping patterns, 0.6.0 behaves like 0.5.0. No API changes.
Changed
-
Ambiguous files that were already processed are ignored. A listed file matching the patterns of several root layouts used to fail the whole run with
AMBIGUOUS_LAYOUT, even if it was old and already imported. Now it is ignored when any of those layouts already covers it:- its timestamp is not after that layout's watermark (with
duplicateProtection.watermark), or - the
alreadyProcessedpredicate reports it.
It is logged at DEBUG. A file none of them covers still fails the run with
AMBIGUOUS_LAYOUT, and a file matching several layouts is never assigned to one of them. Old files left on a server no longer block a definition that gains an overlapping pattern. - its timestamp is not after that layout's watermark (with
Fixed
- With a name matching several patterns, each layout's watermark is compared with the timestamp extracted by its own pattern, not by the last pattern that matched.
Artifacts
| Artifact | |
|---|---|
io.github.tie-integration-engine:tie-core:0.6.0 |
The library |
io.github.tie-integration-engine:tie-jexl:0.6.0 |
Optional programmable fields with Apache Commons JEXL |
io.github.tie-integration-engine:tie-spring-boot-starter:0.6.0 |
Optional Spring Boot 4 auto-configuration |
Available on Maven Central:
<dependency>
<groupId>io.github.tie-integration-engine</groupId>
<artifactId>tie-core</artifactId>
<version>0.6.0</version>
</dependency>The jars, with their sources and javadoc, are attached below. Requires Java 25.
Documentation
- README and CHANGELOG.
- Full diff: v0.5.0...v0.6.0.
- Modules: tie-core, tie-jexl and tie-spring-boot-starter.
TIE 0.5.0
Definitions can now be written back as JSON or YAML, and fields can compute their value with an expression. Programmable fields come with a new optional module, tie-jexl. Without expressions, 0.5.0 behaves like 0.4.0.
Added
DefinitionWriter.toJson/toYaml: a definition built with the Java API, or loaded, written as the documentDefinitionLoaderreads back.- The definition is validated first.
- Keys follow the schema order and defaults are left out, so equal definitions give the same text.
- Literal credentials are written as
***.
- Programmable fields:
expressionon a field computes its final value.- On import, expressions run after the other steps of every field, in declaration order. They see
value, the other fields, the parent record (parent,parent.parent),todayand the context variables. The result is converted to the field's type and validated. - On export, they run over the supplied values.
- New SPI
ExpressionEngine(Tie.Builder.expressionEngine) and line error codeEXPRESSION_FAILED.
- On import, expressions run after the other steps of every field, in declaration order. They see
- New module
tie-jexl:JexlExpressionEngine, with Apache Commons JEXL in a restricted sandbox:- no class access, loops,
newor side effects; - misspelt names are errors;
- functions
tie:age,tie:years,tie:blank,tie:date,tie:formatandtie:coalesce.
- no class access, loops,
- Spring Boot starter: registers a
JexlExpressionEnginewhentie-jexlis on the classpath.
fields:
- { name: birthDate, type: DATE }
- name: idDocument
expression: "value != null ? value : (tie:age(birthDate) < 16 ? parent.idDocument : null)"Tie tie = Tie.builder().expressionEngine(new JexlExpressionEngine()).build();
String yaml = DefinitionWriter.toYaml(definition);Changed
FieldDefinitionhas a newexpressioncomponent, so its canonical constructor changed. The builder is unaffected.- A credential equal to
***, whatDefinitionWriterwrites for a literal one, is now a configuration problem. copyFromof a field with anexpressionis now a configuration problem.
Artifacts
| Artifact | |
|---|---|
io.github.tie-integration-engine:tie-core:0.5.0 |
The library |
io.github.tie-integration-engine:tie-jexl:0.5.0 |
Optional programmable fields with Apache Commons JEXL (new) |
io.github.tie-integration-engine:tie-spring-boot-starter:0.5.0 |
Optional Spring Boot 4 auto-configuration |
Available on Maven Central:
<dependency>
<groupId>io.github.tie-integration-engine</groupId>
<artifactId>tie-core</artifactId>
<version>0.5.0</version>
</dependency>The jars, with their sources and javadoc, are attached below. Requires Java 25.
Documentation
- README and CHANGELOG.
- Full diff: v0.4.0...v0.5.0.
- Modules: tie-core, tie-jexl (new) and tie-spring-boot-starter.
TIE 0.4.0
Records can now be found by position when their name is not known in advance, and layouts fed only by provided inputs no longer need a file name pattern. With the defaults, 0.4.0 behaves exactly like 0.3.0.
Added
- XML imports without
recordElement: every child of the root element is a record, whatever its name; sibling records may have different names. Records are read as before (attributes, dotted paths, nested layouts bynestedKey). Text, comments and processing instructions directly under the root are ignored. Exports still requirerecordElement. json.firstArray: with norecordProperty, the records are the root array or, for a root object, its first top-level property whose value is an array. Earlier properties are skipped in streaming without being read; a root object without any array fails withSTRUCTURAL. It cannot be combined withrecordPropertyon import and is ignored on export.JsonOptionsgets a builder.fileNamePatternis optional on a root import layout when every input channel is aProvidedStreamChannel. A declared pattern is still validated.
inputChannels: [PROVIDED_STREAM]
layouts:
- name: employees # no fileNamePattern: only provided inputs
allowedFormats: [XML, JSON]
formatOptions:
xml: {} # no recordElement: every child of the root is a record
json: { firstArray: true }Changed
JsonOptionshas a newfirstArrayrecord component, so its canonical constructor changed; useJsonOptions.builder().JsonOptions.DEFAULTSkeeps the same values.- A blank (but not null)
xml.recordElementon import is now reported as "must not be blank" instead of "is required".
Artifacts
| Artifact | |
|---|---|
io.github.tie-integration-engine:tie-core:0.4.0 |
The library |
io.github.tie-integration-engine:tie-spring-boot-starter:0.4.0 |
Optional Spring Boot 4 auto-configuration |
<dependency>
<groupId>io.github.tie-integration-engine</groupId>
<artifactId>tie-core</artifactId>
<version>0.4.0</version>
</dependency>The jars, with their sources and javadoc, are attached below. Requires Java 25.
Documentation
- README and CHANGELOG.
- Full diff: v0.3.0...v0.4.0 (modules: tie-core, tie-spring-boot-starter).
TIE 0.3.0
Four additions for reading files as the V2 integration engine did: default values delivered as text, XLSX cells read as Excel displays them, blank XLSX rows skipped, and date patterns with a locale. With the defaults, 0.3.0 behaves exactly like 0.2.0.
Added
defaultModeon a field withdefaultValue:CONVERT(default, the 0.2.0 behaviour) orTEXT. WithTEXTthe resolved default skips type conversion, still goes through the field's validations, and reaches the consumer as aStringwhatever the field's type, so an unresolved${…}template in aDATEfield no longer rejects the line.- XLSX reading options:
skipBlankRecords, as in CSV: a row whose cells are all blank is dropped and uses no line number.cellValues: FORMATTEDreads numbers and dates as Excel displays them per the cell's number format (08001,25%,1,234.50,15/03/2024,12345678A);CANONICALremains the default.locale(BCP 47, defaultROOT) sets the separators and names forFORMATTED:1.234,50withes-ES.XlsxOptionshas a builder.
- Date patterns with a locale:
TypeFormat.date(pattern, locale)ortypeFormat: { pattern, locale }, for month and day names and AM/PM when reading and writing (31-dic-2026withes-ES).
formatOptions:
xlsx: { cellValues: FORMATTED, locale: es-ES, skipBlankRecords: true }
fields:
- { name: signed, type: DATE, typeFormat: { pattern: dd-MMM-yyyy, locale: es-ES } } # 31-dic-2026
- { name: loaded, inInput: false, type: DATE, defaultValue: "${loadDate}", defaultMode: TEXT }Changed
RecordView.get(field)is no longer always of the field's Java type: adefaultMode: TEXTfield that took its default holds aString, andget(field, LocalDate.class)throwsClassCastExceptionfor it. This only affects fields that declareTEXT.- Canonical constructors of
XlsxOptions(useXlsxOptions.builder()),TypeFormat.DateFormatandFieldDefinitionhave new components; record patterns onDateFormat(String pattern)no longer compile.XlsxOptions.DEFAULTS,TypeFormat.date(pattern)and the builders are unchanged.
Artifacts
| Artifact | |
|---|---|
io.github.tie-integration-engine:tie-core:0.3.0 |
The library |
io.github.tie-integration-engine:tie-spring-boot-starter:0.3.0 |
Optional Spring Boot 4 auto-configuration |
Available on Maven Central:
<dependency>
<groupId>io.github.tie-integration-engine</groupId>
<artifactId>tie-core</artifactId>
<version>0.3.0</version>
</dependency>The jars, with their sources and javadoc, are attached below. Requires Java 25.
Documentation
- README and CHANGELOG.
- Full diff: v0.2.0...v0.3.0 (modules: tie-core, tie-spring-boot-starter).
TIE 0.2.0
Two contract changes to the import engine: file hooks now run for provided inputs, and field copies can take the canonical value of their source.
Added
copyModeon a field withcopyFrom:TEXT(default, the 0.1.0 behaviour) orCANONICAL, in the Java API, YAML/JSON and the JSON schema.- With
CANONICAL, an imported copy receives the canonical text of the source's typed value (2026-12-31,1234.50,true), whatever the source'stypeFormat, so two files with the same date written in different formats give the same copy. - When the source is not
STRINGand the copy's own trimming, transforms, translations and transformer leave that text unchanged, the target tries the canonical form before itstypeFormat. - Ignored on export, where a copy already takes the source's supplied value.
copyModewithoutcopyFromis a configuration error.
- With
fields:
- { name: born, type: DATE, typeFormat: dd/MM/yyyy }
- { name: bornIso, inInput: false, copyFrom: born, copyMode: CANONICAL } # 2026-12-31Changed
FileHookis called for provided inputs too. With a hook registered, a provided input is spooled once to the working directory and getsonFileReceived(nulltimestamp,size= bytes read) andonFileCompleted, like a channel file. Without a hook nothing changes. If you register aFileHookand use provided inputs, it now receives these calls.FieldDefinitionhas a newcopyModerecord component aftercopyFrom, so its canonical constructor changed. Code using the builder is unaffected.
Artifacts
| Artifact | |
|---|---|
io.github.tie-integration-engine:tie-core:0.2.0 |
The library |
io.github.tie-integration-engine:tie-spring-boot-starter:0.2.0 |
Optional Spring Boot 4 auto-configuration |
Available on Maven Central:
<dependency>
<groupId>io.github.tie-integration-engine</groupId>
<artifactId>tie-core</artifactId>
<version>0.2.0</version>
</dependency>The jars, with their sources and javadoc, are attached below. Requires Java 25.
Documentation
- README and CHANGELOG.
- Full diff: v0.1.0...v0.2.0 (modules: tie-core, tie-spring-boot-starter).
TIE 0.1.0
First release of TIE, a stateless Java library for file integrations.
Highlights
- Imports from SFTP, local directories and provided streams; exports and
deliverFileto the same channels. - CSV, XLSX, XML and JSON, read and written incrementally: memory is bounded by one record, not by the file.
- Typed field engine: column lookup by header, position or letter; copies, trimming, text transforms, translation tables, custom transformers, type conversion, validations, empty-value rules and default values.
- Nested child records in JSON and XML.
- Delivery strategies
STREAMINGandVALIDATE_THEN_DELIVER, rejection thresholds, consumer error policies, cancellation, run listener and file hooks. - Stateless duplicate protection: watermarks, an already-processed predicate, and move or delete after success.
- Safe deliveries: temporary
.<name>.partfile, final rename,onExistingFile(SUFFIX,FAIL,OVERWRITE). - Result reports in CSV, XLSX, JSON and XML.
- Declarative definitions in YAML or JSON, with a published JSON schema.
- Stable catalogs of line error codes, file error types and warning codes.
- Spring Boot 4 starter.
Requirements
Java 25. tie-core has no Spring dependency.
Artifacts
| Artifact | |
|---|---|
io.github.tie-integration-engine:tie-core:0.1.0 |
The library |
io.github.tie-integration-engine:tie-spring-boot-starter:0.1.0 |
Optional Spring Boot 4 auto-configuration |
Available on Maven Central:
<dependency>
<groupId>io.github.tie-integration-engine</groupId>
<artifactId>tie-core</artifactId>
<version>0.1.0</version>
</dependency>The jars, with their sources and javadoc, are also attached below.