michael-hoke commented on issue #170: URL: https://github.com/apache/daffodil-vscode/issues/170#issuecomment-1208702620
Sorry for my lack of response on this for so long, but I did take your feedback, and I believe I am getting close to having a PR ready. I'm hoping we can start resolving any issues you think are outstanding before the introduction of the PR. Scala vs Java: I ended up using Scala for the necessary back end changes. This likely would have been inevitable due to how tied to the execution of DFDL that the new TDML operations are. Daffodil's TDML Runner: I looked into this briefly but ended up sticking with JAXB for the initial version. I believe the JAXB portion of the code has been modularized enough so that if someone wants to extend this effort and share the TDMLRunner between this repo and the Daffodil repo, they should be able to do so without too much headache. Scalaxb: I did some more digging into the possibility of us using scalaxb over JAXB, but it did not look positive for us. In order to get JAXB to work, I had to create a fairly straightforward bindings file. Most, if not all, of the bindings were needed to rename components of the XML that happened to have the same name. I was hoping that scalaxb would be able to take a bindings file, similar to JAXB. Unfortunately, not only is there no command line argument for a bindings file, but there are command line arguments to do the renaming. However, the renaming is done based on component type (i.e. rename elements or rename attributes), and we have at least one case in the TDML schema where two different attributes share the same name, so scalaxb's existing command line arguments would not be enough for us. So, that being said, it might be best to not expect to move to scalaxb in the future. We already have JAXB working, and a shared TDMLRunner is probably a better long term goal. Other than that, the repo itself doesn't have any commits since the beginning of the year, and the last thing in the repo's gitter chat is my question about the renaming issue that I posted about 2.5 months ago. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
