Releases: xlate/staedi
v1.16.0 - XML Transaction Content Wrapper
v1.15.0 - TRADACOMS Support
Change summary:
[ #154 ] Introduce TRADACOMS dialect support
v1.14.2 - Bug Fixes & Improvements
v1.14.0 - Json Parser Support
Change Summary
[ #133 ] Add initial implementation of JsonParser
(either javax
or jakarta
package version may be used) to support reading an EDI stream as if it is JSON. See EDIInputFactory.createJsonParser
. The expected parser type is passed as an argument (either jakarta.json.stream.JsonParser
or javax.json.stream.JsonParser
initially). Support for the equivalent JsonGenerator
s is planned and support for Jackson may be added in the future if requested.
[ #134 ] Fix issue where data elements were treated as repeating occurrences when writing XML to JSON
v1.13.0 - Ignore Extraneous Characters & New Scale Attribute
Change summary:
[ #128, #130 ] Add option to ignore extraneous (control, certain white space) characters in EDI input. See documentation on wiki for more details.
[ #131, #132 ] Add scale
attribute to schema element type. The attribute has no impact on EDI validation and is intended for documentation purposes only.
v1.12.0 - Fixes & Simpler XML Writing
v1.11.0 - Output Element Padding & Non-ASCII Delimiters
Change summary:
[ #102, #105 ] Support firstonly
syntax validation (EDIFACT D7) - Enhancement
[ #106, #107 ] Clear Validator
element fields upon validation of new segment - Bug fix
[ #109, #110 ] Support non-ASCII delimiter characters - Enhancement
[ #108, #111 ] Add option to format (pad) output elements to minimum required lengths. See the writer configuration wiki page for more information on the FORMAT_ELEMENTS
configuration property - Enhancement
v1.10.2 - Fix Access to Implementation Elements via EDIStreamReader
This bug fix release builds on release 1.10.1
to ensure that implementation composites/elements in a segment that occur prior to the discriminator element (identified in the schema) are properly made available to the EDIStreamReader
via the getSchemaTypeReference
method. It is a known issue that any implementation constraints for the elements will not be validated (to be fixed via #88 in a future release)
Change summary:
[ #87, #91 ] Update event array element types upon implementation segment selection
v1.10.1 - Fix Access to Implementation Types via EDIStreamReader
Change summary:
[ #86 ] Return impl schema types from validator when available