[jira] [Updated] (DAFFODIL-1747) Remove separate sapi and japi

["Mike Beckerle (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DAFFODIL-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Beckerle updated DAFFODIL-1747:
------------------------------------
    Priority: Minor  (was: Major)

> Remove separate sapi and japi
> -----------------------------
>
>                 Key: DAFFODIL-1747
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1747
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: API, Clean Ups
>    Affects Versions: 2.0.0
>            Reporter: Steve Lawrence
>            Priority: Minor
>
> The two API's are virtually the same. The only real differences are:
> * Java Lists vs Scala Seqs
> * Java Map vs Scala Map
> * Logger enums
> * parse outputs a JDOM Document vs Scala XML Node
> * unparse inputs a JDOM Document vs Scala XML Node
> Replacing Scala Seq/Map/enums with a Java List/Map/enum does not seem that big of a deal. And with new InfosetInputter and InfosetOutputters, the differences between parse and unparse are removed. Since we are already breaking API with the addition of InfosetInputter/Outputter, we should just remove the sapi/japi distinction and just have a daffodil-api class that will work for both Java and Scala, removing the duplicate code.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)