Hi Weber,
The Apache Daffodil 2.2.0 API introduced the InputSourceDataInputStream
class as the preferred way to provide data to Daffodil. This constructor
accepts either a byte array, a java.nio.ByteBuffer, or a
java.io.InputStream. Hopefully your shared memory interface can be
represented as one
Hello,
We are exploring ways to use Daffodil for data normalization.
The data comes in to our system via a protocol adapter which it then copies to
a shared memory interface. Getting that data into Daffodil is not
straightforward, it seems to only read from files which we are trying to
Created and pushed these branches for all the fouo schemas on di2e.net as well.
There are a few changes there besides the build.sbt 2.2.0-SNAPSHOT version
change. Recent changes have made use of xsi:schemaLocation on the root element
of TDML files or DFDL schemas cause warnings from Xerces.
I've created branches named for-daffodil-2.2.0 which request 2.2.0-SNAPSHOT of
daffodil, for these DFDLSchemas on github
bmp
CSV
gif
jpeg
mil-std-2045
NACHA
NITF
PCAP
png
quasiXML
This facilitates testing these against the daffodil 2.2.0 development branch
, dbe98c1065d6874471f271124627fbe3e346976f.
Verified that the has been updated to 2.2.0.
> Prepare for Daffodil 2.2.0 development
> --
>
> Key: DAFFODIL-1936
> URL: https://issues.apache.org/jira/brows
in dbe98c1065d6874471f271124627fbe3e346976f
> Prepare for Daffodil 2.2.0 development
> --
>
> Key: DAFFODIL-1936
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1936
> Project: Daffodil
>
Steve Lawrence created DAFFODIL-1936:
Summary: Prepare for Daffodil 2.2.0 development
Key: DAFFODIL-1936
URL: https://issues.apache.org/jira/browse/DAFFODIL-1936
Project: Daffodil
Issue
