You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Michael Beckerle (JIRA)" <ji...@apache.org> on 2018/10/24 23:52:00 UTC

[jira] [Commented] (DAFFODIL-1639) IBM Compatibility - EDIFACT

    [ https://issues.apache.org/jira/browse/DAFFODIL-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663021#comment-16663021 ] 

Michael Beckerle commented on DAFFODIL-1639:
--------------------------------------------

Tried EDIFACT on Daffodil 2.2.0.

Compiles, but the test fails. All the features supposedly needed for EDIFACT are implemented, so this non-portability needs to be figured out.

My current theory this is related to sequences with separators, and dfdl:separatorSuppressionPolicy. (Need to verify that.)

> IBM Compatibility - EDIFACT
> ---------------------------
>
>                 Key: DAFFODIL-1639
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1639
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: Compatibility, DFDL Schemas, Integrations
>    Affects Versions: 2.0.0
>            Reporter: Michael Beckerle
>            Priority: Major
>              Labels: ForInteroperabilityTest
>             Fix For: 2.3.0
>
>
> DFDLSchemas EDIFACT doesn't yet work.
> As of this writing these issues are blocking it, or blocking working on it sufficiently that they have to be fixed first.
> DFDL-1443 - escapeScheme expressions evaluated before we know there are any delimiters to escape
> DFDL-256 - ignoreCase - this is used by edifact, unclear if it is truly needed for the tests to work or not.
> DFDL-1166 - TDML runner needs to load a saved parser - it takes a very long time to compile this schema (many minutes).  DFDL-1444 is the ticket for separate compilation, but just compiling with less memory footprint and faster would help.
> Currently compiling the EDIFACT schema requires sbt -mem 8000m 
> Otherwise it dies a long death as it runs out of memory, and all threads are busy scavenging it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)