|
|
|
Re: Using QVTo with Xtext [message #1786067 is a reply to message #1786046] |
Wed, 25 April 2018 07:07 |
Daniel Strueber Messages: 11 Registered: April 2014 |
Junior Member |
|
|
Thanks, Rolf and Ed!
Saving the transformation result as .xmi was a good idea: When I do this, the transformation works. Since I get the stack trace only when I set the output file to have the .B file extension, the problem must come from the Xtext serialization.
The problem may indeed come from a mis-configuration, but unfortunately I don't find any choice in the "Run Configuration" dialog that would allow me to specify how the Xtext serialization should be used. I only changed three settings in the dialog: the paths to the transformation module, the IN file, and the OUT file.
For now, one workaround for my use-case would be to chain the transformation to XMI with some additional code that loads the XMI and persists it to the Xtext serialization. But I wonder if there's a less cumbersome way to do it.
[Updated on: Wed, 25 April 2018 07:17] Report message to a moderator
|
|
|
|
Re: Using QVTo with Xtext [message #1786081 is a reply to message #1786073] |
Wed, 25 April 2018 10:06 |
Daniel Strueber Messages: 11 Registered: April 2014 |
Junior Member |
|
|
Thanks again! Ed, I think you're on the right track by pointing out that the serialization is a bit fragile. I now found out that I can get the "gory-detail" error messages by converting the generated XMI to the Xtext format using "Save as", as suggested by Rolf. And there it seems that the serialization struggles with finding an appropriate way for dealing with certain cross-references that I need in my B files. This is then more of a Xtext problem than a QVTo problem, so I will look further into that direction.
[Updated on: Wed, 25 April 2018 10:06] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.03755 seconds