-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support JSON as a serialization format for ModelInfo #640
Comments
@brynrhodes Is this still open? Or now resolved? |
Folks, I am going to need this. So, how should this be done? Should the project abandon the XML representation to use JSON only or is the project sustaining both? |
Hi @vitorpamplona , we can't abandon it but we can restructure the dependencies, that's the next step here, to separate out the "hardcoded" nature of the modelinfo loading and make sure we can do it dynamically. One easy thing we can try (and I just haven't yet) is to see if the Jackson library actually can deserialize the XML modelinfo. Modelinfo is a much simpler structure, so it may just work (The reason we can't use the ELM XML is because it has the JAXB dependencies, not because we can't deserialize XML at all, right?) |
I am happy to report that it largely works (with some tweaks). But I am having a hard time figuring out what is wrong with the USCore and QICore packages. See PR #745 |
The translator currently only supports XML deserialization of model info, which means there is not a good story for deserialization of model info files in the Android space, which effectively prevents the translator from being used in an Android environment.
The text was updated successfully, but these errors were encountered: