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/11/28 16:04:00 UTC

[jira] [Created] (DAFFODIL-2023) API reload(...) should not require a Channel. An input stream, URI, or byteArray should work.

Michael Beckerle created DAFFODIL-2023:
------------------------------------------

             Summary: API reload(...) should not require a Channel. An input stream, URI, or byteArray should work.
                 Key: DAFFODIL-2023
                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2023
             Project: Daffodil
          Issue Type: Improvement
          Components: API
    Affects Versions: 2.2.0
            Reporter: Michael Beckerle


For JAPI, SAPI, and the regular internals, the use of Channels everywhere instead of regular java io streams is annoying.

For DataProcessor.save, and compiler.reload, we should accept ordinary java.io.InputStream and java.io.OutputStream. 

No point in making a java programmer understand Channels to use a simple API like this. 

Our use of channels may be ill-advised here anyway. I can't recall the rationale for choosing them to begin with. 





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