Home » Modeling » QVT-OML » Modifying QVT Traceability.
| Modifying QVT Traceability. [message #899805] |
Thu, 02 August 2012 12:06  |
 Juan Pedro Silva
Messages: 258
Registered: July 2009 |
Senior Member |
|
|
Hi everybody!.
I'm new to QVT, although not that new to Eclipse plugins, EMF and M2M.
Congratulations on your tool, by the way.
We are planning on using QVTO on a research project now, and we would be
interested in modifying some of its functionality.
In particular, we are interested in using a more customized/elaborated
traceability metamodel that is more adjusted to our particular needs.
I would like to ask, therefore, if there is any extension point in QVTO
where we could plug-in a new traceability metamodel and engine.
One of my partners has already modified QVTO to take the trace model as
input and only create new elements (sort of incremental transformation),
but this implies playing with internal classes.
We would prefer to use a more maintainable extension approach, and that
is the reason behind my question.
Thanks in advance for your help.
Regards,
JP
|
|
|
| Re: Modifying QVT Traceability. [message #899816 is a reply to message #899805] |
Thu, 02 August 2012 12:42  |
Ed Willink
Messages: 7655
Registered: July 2009 |
Senior Member |
|
|
Hi
I doubt that there is such a capability.
QVTo may gradually move to the new Eclipse OCL VM which is more
accurate, faster, flexible and has a Java code generator.
The flexibility might help you one day.
QVTo is short of developers so if you want something special you may
have to help yourself, or join in a collaboration for the future.
Regards
Ed Willink
On 02/08/2012 13:06, Juan Pedro Silva Gallino wrote:
> Hi everybody!.
> I'm new to QVT, although not that new to Eclipse plugins, EMF and M2M.
> Congratulations on your tool, by the way.
> We are planning on using QVTO on a research project now, and we would
> be interested in modifying some of its functionality.
> In particular, we are interested in using a more customized/elaborated
> traceability metamodel that is more adjusted to our particular needs.
>
> I would like to ask, therefore, if there is any extension point in
> QVTO where we could plug-in a new traceability metamodel and engine.
> One of my partners has already modified QVTO to take the trace model
> as input and only create new elements (sort of incremental
> transformation), but this implies playing with internal classes.
> We would prefer to use a more maintainable extension approach, and
> that is the reason behind my question.
>
> Thanks in advance for your help.
> Regards,
> JP
|
|
|
| Re: Modifying QVT Traceability. [message #899824 is a reply to message #899816] |
Thu, 02 August 2012 13:19 |
Juan Pedro Silva
Messages: 258
Registered: July 2009 |
Senior Member |
|
|
Thank you, Ed, for your answer.
We might upload a patch or something to a bugzilla enhancement if we
follow this path.
Nonetheless, from your comment on a migration to the new OCL VM I get
that (mayor) changes are expected on internal classes, so this will
probably not be a safe path to follow (having compatibility with future
QVTO versions in mind).
Regards,
JP
El 02/08/2012 14:42, Ed Willink escribió:
> Hi
>
> I doubt that there is such a capability.
>
> QVTo may gradually move to the new Eclipse OCL VM which is more
> accurate, faster, flexible and has a Java code generator.
>
> The flexibility might help you one day.
>
> QVTo is short of developers so if you want something special you may
> have to help yourself, or join in a collaboration for the future.
>
> Regards
>
> Ed Willink
>
> On 02/08/2012 13:06, Juan Pedro Silva Gallino wrote:
>> Hi everybody!.
>> I'm new to QVT, although not that new to Eclipse plugins, EMF and M2M.
>> Congratulations on your tool, by the way.
>> We are planning on using QVTO on a research project now, and we would
>> be interested in modifying some of its functionality.
>> In particular, we are interested in using a more customized/elaborated
>> traceability metamodel that is more adjusted to our particular needs.
>>
>> I would like to ask, therefore, if there is any extension point in
>> QVTO where we could plug-in a new traceability metamodel and engine.
>> One of my partners has already modified QVTO to take the trace model
>> as input and only create new elements (sort of incremental
>> transformation), but this implies playing with internal classes.
>> We would prefer to use a more maintainable extension approach, and
>> that is the reason behind my question.
>>
>> Thanks in advance for your help.
>> Regards,
>> JP
>
|
|
|
| Re: Modifying QVT Traceability. [message #899903 is a reply to message #899824] |
Thu, 02 August 2012 18:25 |
Ed Willink
Messages: 7655
Registered: July 2009 |
Senior Member |
|
|
Hi
Significant evolution is likely, but not on traceability. If you can
identify a more flexible traceability framework, it could be adopted by
the enhanced QVTo, and possibly QVTc ....
I envision some kind of base model that defines a minimal API.
Regards
Ed Willink
On 02/08/2012 14:19, Juan Pedro Silva Gallino wrote:
> Thank you, Ed, for your answer.
> We might upload a patch or something to a bugzilla enhancement if we
> follow this path.
>
> Nonetheless, from your comment on a migration to the new OCL VM I get
> that (mayor) changes are expected on internal classes, so this will
> probably not be a safe path to follow (having compatibility with
> future QVTO versions in mind).
>
> Regards,
> JP
>
>
> El 02/08/2012 14:42, Ed Willink escribió:
>> Hi
>>
>> I doubt that there is such a capability.
>>
>> QVTo may gradually move to the new Eclipse OCL VM which is more
>> accurate, faster, flexible and has a Java code generator.
>>
>> The flexibility might help you one day.
>>
>> QVTo is short of developers so if you want something special you may
>> have to help yourself, or join in a collaboration for the future.
>>
>> Regards
>>
>> Ed Willink
>>
>> On 02/08/2012 13:06, Juan Pedro Silva Gallino wrote:
>>> Hi everybody!.
>>> I'm new to QVT, although not that new to Eclipse plugins, EMF and M2M.
>>> Congratulations on your tool, by the way.
>>> We are planning on using QVTO on a research project now, and we would
>>> be interested in modifying some of its functionality.
>>> In particular, we are interested in using a more customized/elaborated
>>> traceability metamodel that is more adjusted to our particular needs.
>>>
>>> I would like to ask, therefore, if there is any extension point in
>>> QVTO where we could plug-in a new traceability metamodel and engine.
>>> One of my partners has already modified QVTO to take the trace model
>>> as input and only create new elements (sort of incremental
>>> transformation), but this implies playing with internal classes.
>>> We would prefer to use a more maintainable extension approach, and
>>> that is the reason behind my question.
>>>
>>> Thanks in advance for your help.
>>> Regards,
>>> JP
>>
>
|
|
|
Goto Forum:
Current Time: Thu Apr 25 13:42:02 GMT 2024
Powered by FUDForum. Page generated in 0.02803 seconds |
] 
Search
Help
Register
Login
Home
