-
Notifications
You must be signed in to change notification settings - Fork 16
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
Resolving "xmi" namespace #16
Comments
I'm afraid that's not easily possible. You would need an ecore representation of the XMI model. If I have understood your question correctly, you can find an answer for a possible way here: Hope this helps! Best regards, |
Hello Mario, I have looked again into the example xmi (euclidian space) mentioned by you. In the section 'Top level object' two versions of serialization are shown: <xmi:XMI xmi:version="2.0" ...> or <EuclideanSpace xmi:version="2.0" ...>. Currently we only support the second version. So if you change the structure of your xmi you might be able to parse it. If we find the time we will support the first form in an upcoming version of emf4cpp. This requires a change in the implementation of the XMLResource framework. Best regards, |
Hi Soeren, thank you for taking time to reply to my request! It helps me to ensure that I'm not using emf4cpp in a wrong way. I'll try to transform my XMI file from the Should I close this issue or do you need it for the further implementations? Best regards |
Hi,
I'm trying to parse a XMI file which has a
xmi:XMI
root node (like shown in the example at https://www.euclideanspace.com/software/information/xml/xmi/index.htm):If I try to parse this file, I get the following error:
I think that the reason is that there's no meta model found in the MetaModelRepository for the namespace
xmi
.This is the code I'm using to register the meta models in the repository:
Do I have to add another package to the registry to be able to parse XMI files with a
xml:XMI
root node?Thank you in advance!
Best regards,
Mario
The text was updated successfully, but these errors were encountered: