Uploaded image for project: 'Daffodil'
  1. Daffodil
  2. DFDL-1747

Remove separate sapi and japi

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.0
    • Fix Version/s: deferred
    • Component/s: API, clean ups
    • Labels:
      None

      Description

      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.

        Gliffy Diagrams

          Attachments

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              slawrence Steve Lawrence
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:

                  Tasks

                  Progress: 
                   0/0