Forwarding to standard support email, as I am tied up on other matters today.
________________________________ From: Magliocca, Matthew - 1004 - MITLL <[email protected]> Sent: Friday, October 25, 2019, 11:33 AM To: Beckerle, Mike Cc: Shannon, Tod - 1004 - MITLL; Ledder, William - 1004 - MITLL; Chiang, Carol - 1004 - MITLL Subject: DFDL VMF 0.0.7 Question Hi Mike, I had a question for you. I’ve taken the updated 0.0.4 and 0.0.7 versions of the VMF DFDL schema and I’m trying to integration-test it against our code. Most things seem to work fine but when we use blocking input streams to supply DFDL with binary data, I’m noticing something kind of odd. When I debug our code I see that DFDL reads the full number of bytes in our binary messages but then seems to go back to the stream and ask for more. If the InputStream it is reading is nonblocking and returns a “-1” character after the message, the system works fine. However if we use blocking input streams the system seems to hang; with DFDL waiting forever for more data without ever returning a completed infoset. I was wondering if there had been a paradigm shift in DFDL dealing with blocking inputstreams in underlying code. The reason I ask if because I noticed you had added a “messageSets” element to the schema and I thought you might have been attempting to use that to group messages rather than handing them back individually. Could the changes we’ve seeing be related to any paradigm shifts in DFDL or is that unlikely? Thanks a lot Matt Mags
