| [QVTO] Custom data types [message #868688] |
Wed, 02 May 2012 08:04  |
Eclipse User |
|
|
|
Hello,
in our EMF model we're using a few custom data types, for which we just
define the FQ class name. Quite obviously, the QVTo editor and engine
don't know how to handle this type. For now I could get by this by using
the generic .repr() function which seems to just the a String
representation. (For some reason, toString() was not available for these
types?!). Is there a more precise approach to this problem? I found
mentioning of the EP org.eclipse.m2m.qvt.oml.ocl.libraries by means of
which -- I think, but just as well I'm mixing concepts here -- one could
extend QVT according to new types, but apparently that one doesn't exist
anymore.
Any insights or pointers appreciated, I just couldn't find anything.
TIA
Marius
|
|
|
| Re: [QVTO] Custom data types [message #868696 is a reply to message #868688] |
Wed, 02 May 2012 08:16  |
| Eclipse User |
|
|
|
Hi
Black boxes seem to be the solution to facilities that are easily
implemented in Java.
Regards
Ed Willink
On 02/05/2012 13:04, Marius Gröger wrote:
> Hello,
>
> in our EMF model we're using a few custom data types, for which we just
> define the FQ class name. Quite obviously, the QVTo editor and engine
> don't know how to handle this type. For now I could get by this by using
> the generic .repr() function which seems to just the a String
> representation. (For some reason, toString() was not available for these
> types?!). Is there a more precise approach to this problem? I found
> mentioning of the EP org.eclipse.m2m.qvt.oml.ocl.libraries by means of
> which -- I think, but just as well I'm mixing concepts here -- one could
> extend QVT according to new types, but apparently that one doesn't exist
> anymore.
>
> Any insights or pointers appreciated, I just couldn't find anything.
>
> TIA
> Marius
|
|
|
Powered by
FUDForum. Page generated in 0.04780 seconds
Home