-
Notifications
You must be signed in to change notification settings - Fork 29
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
Issue with Xml serialization #14
Comments
Development ongoing in the branch 14-issue-with-xml-serialization. |
Hi @christianhecht86 , Thanks! |
Hi @christianhecht86 , |
Hi @girishchandranc , unfortunately it solves not the entire issue. Please see my email. Christian |
Hi @christianhecht86 , |
Hi @girishchandranc , now it looks much better. Only two things...
code: ARXML: For some Lists, there should be a tagged value isOrdered="true" in the ecore definition. Here it is important to keep the ordering. Christian |
Hi @christianhecht86 , Can you please check together with the issues you reported via email to see it the latest commit satisfies all the issues reported. |
Hi @girishchandranc , thank you for your hard work to fix the serialization issues. In current version my reported issues are solved. So, from my point of view, you should merge it to master branch. Christian |
The xml elements are created on the fly whenever the api's are used and this isn't ideal and could lead to schema violations. This needs a rework on the way xml is serialized.
The text was updated successfully, but these errors were encountered: