Looking through the Java docs, I assume no but I wanted to verify.
What Steve said. But I would add that we set priorities based on what our users need, and would be happy to help you out. The API is less the problem than the fact that unparser support is really pretty limited still, and can't unparse many formats that can be successfully parsed.
Filling in the unparser support (and the API for it) is a very high priority, actually our highest priority currently, though we're not planning any releases with additional functionality until later this year or early next.
As of Daffodil version 1.1.0, there is not a public API available for unparsing. However, the "unparse" command with the CLI can perform unparsing (though, note that unparse capabilities are fairly limited in 1.1.0). Also, note that in Main.scala there is code that uses an internal API, which could be used to implement unparse support in our project, but that API is considered unstable and could change between releases.
Thanks for the responses Mike ad Stephen. Let me check to see if we can wait until year end on our project.
Regarding Main.scala and the internal API.. I'm new to Scala... How would I call the code in Main.scala within my Java code to leverage unparse?
I should have mentioned this in my earlier reply, but using the internal API (which is Scala) with Fava would be pretty difficult, and is realistically only an option if you're already coding in Scala. Not only is it difficult, sometimes it's not even possible. For example, Scala can have function names that aren't legal in Java, so you might not even be able to call some functions. And in the cases where Java can call Scala code, it can be quite difficult because of the amount of generated code and classes that Scala creates, making it very unclear what classes/functions need to be created/called. So, although it's possible, I would not recommend using Main.scala as a base for adding unparse support unless you were coding in Scala.
Also note that in 1.1.0, unparse feature implementation is fairly limited, supporting only a subset of text related features. Our current development branch does implement some more unparse features, but even today, unparse lags behind parse support by quite a bit.
Has any progress been made on unparsed? specifically looking for Java.
Yes, the Daffodil 2.0.0 release has full support for unparsing, including Java and Scala APIs. The Java API is available here: https://opensource.ncsa.illinois.edu/projects/artifacts/DFDL/2.0.0/documentation/Javadoc/
Thanks! That is what I get for just reading the question and not looking at the API first. Sorry about that.
Powered by a free Atlassian Confluence Open Source Project License granted to NCSA OpenSource. Evaluate Confluence today.