v1.9.4 - Bug Fix for Empty Impl. Segments at Loop Start

Change summary:
[ #79 , #80 ] Correct implementation segment selection at loop start for single match

v1.9.3 - Bug Fix for X12 GE Segment Validation

Change summary:
[ #74, #76 ] Correct order of GE segment's elements in X12 control schema

v1.9.2 - Bug Fixes for Unexpected Exceptions

Change summary:

• [ #68, #69 ] Delay EDIFACT version parse until end of composite element UNB01. Previously incorrect assumptions were made about the element sizes to determine when to initiate parsing the version.
• [ #70, #71 ] Throw EDIStreamException immediately from Lexer#parser in INVALID state. When using a filtered XMLStreamReader from StAX (xerces implementation in OpenJDK), exceptions thrown from the Lexer during the filter's initialization are swallowed. This change allows them to be correctly thrown again when the filter is first used.

v1.9.1 - Pretty Print Bug Fix

Change summary:

[ #64, #65 ] Ignore pretty print output option when segment terminator is newline character

v1.9.0 - Reader, Writer, and Validation Enhancements

Change summary:
[ #52, #53 ] Add interface to report output errors; align name for input reporter
[ #45, #54, #55 ] Enable retrieval of current schema reference from reader/writer; Add method to retrieve the current transaction version from reader
[ #42, #56 ] Support syntax relationships between loops and/or segments. For example, EDIFACT CONTRL may only contain either group responses or message responses, not both.
[ #51, #58 ] Support X12 ISX Segment Release Character. Version 007040 of X12 added the ISX segment, the first element of which allows for the use of a release character to escape special characters in the interchange (similar to using \ in a Java string literal). This is the same functionality allowed by the EDIFACT release character.

v1.8.1 - Control Schema Bug Fix

Fix a serious bug preventing internal library control schemas from loading properly, commit 79365cc.

v1.8.0 - New Schema Version 4

There are lots of changes in this release! Many are dealing with a new version of the EDI schema. To take advantage of the new schema, the http://xlate.io/EDISchema/v4 namespace must be used. Note that the V4 schema has removed the ref attribute from type references and requires the use of type instead (replace ref= by type= in your schema files).

Change Summary

• [ 681fba6 ] Add EDIStreamWriter#getDelimiters, auto-write UNA for EDIFACT if needed
• [ #38, #39, #48, #50 ] Support an <include> element in schema files to allow EDI schema reuse, extensions. To use this feature, the http://xlate.io/EDISchema/v4 namespace must be used in your <schema>.
• [ 58793d4 ] Support X12 ISB segment in out-of-the-box control schemas
• [ c40d367 ] Support X12 ISE segment in out-of-the-box control schemas
• [ 71c7725 ] Allow versions for elementType, validate X12 GS date based on version. This allows a single schema to handle multiple versions of a standard when the difference is dealing the size or code value constraints for an element.
• [ 63f65e4 ] Consider dialect-specific transaction version when validating occurrences of elements/composites
• [ #40, #41 ] Add SchemaFactory.SCHEMA_LOCATION_URL_CONTEXT property. Allows for the relative URLs (besides relative to working directory) to be used in the schemaLocation attribute of the include element.
• [ #46, #47 ] Add option to suppress trailing empty elements, EDIOutputFactory.TRUNCATE_EMPTY_ELEMENTS

v1.7.1 - Bug Fixes for Multiple Transactions

Change summary:

[ #35 , #36 ] Reset validator at start of transaction/message
[ 83fa058 ] Bug fixes in X12 dialect, schema retrieval, and Location#toString

v1.7.0 - Enhanced Character Encoding Support

Change summary:

[#25, #26] Add getStandard method to EDIStreamWriter
[#33. #34] Decode input characters and encode output using provided Charset name

Note: Developers using EDIStreamWriter must be aware that the method of output encoding introduced in #34 utilizes a buffer and a call to flush() or close() is critical after writing all segments and elements. An explicit flush is not necessary when endInterchange() is used.

v1.6.0 - Lax Element / Composite Validation

Change summary:

[4862d4e] Throw EDIStreamException if end of input reached before grammar complete (runtime)
[028145c] Allow transaction schema to be set through the header's END_SEGMENT (API)
[56d30af] Add option to declare xmlns attributes on TRANSACTION element (API, EDIInputFactory option)
[#23, #24] Support for lax validation of simple elements and composite elements