Fuse 6 is no longer supported
As of February 2025, Red Hat Fuse 6 is no longer supported. If you are using Fuse 6, please upgrade to Red Hat build of Apache Camel.이 콘텐츠는 선택한 언어로 제공되지 않습니다.
2.14. EDI to SAX Event Mapping
When mapping EDI to SAX events, segments are matched in either of these ways:
- by an exact match on the segment code (segcode).
- by a regex pattern match on the full segment, where the segcode attribute defines the regex pattern (for instance,
segcode="1A\*a.*"
). - required: field, component and sub-component configurations support a "required" attribute, which flags that field, component or sub-component as requiring a value.
- by default, values are not required (fields, components and sub-components).
- truncatable: segment, field and component configurations support a "truncatable" attribute. For a segment, this means that parser errors will not be generated when that segment does not specify trailing fields that are not "required" (see "required" attribute above). Likewise for fields/components and components/sub-components.
- By default, segments, fields, and components are not truncatable.
So, a field, component or a sub-component can be present in a message in one of the following states:
- present with a value (
required="true"
) - present without a value (
required="false"
) - absent (
required="false" and truncatable="true"
)