Eclipse Community Forums: EMF "Technology" (Ecore Tools, EMFatic, etc) » [EMF Compare] Questions wrt EMF-DIFF file

Help

Home

Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » [EMF Compare] Questions wrt EMF-DIFF file

Show: Today's Messages :: Show Polls :: Message Navigator

[EMF Compare] Questions wrt EMF-DIFF file [message #88104]

Thu, 05 July 2007 11:07

Eclipse User

Originally posted by: user.domain.invalid

After some discussion....

All the modelers etc are more than happy with the tool as is but as
usual....Management want something simple....i.e. an HTML page/Tabular
view which is basically the top pane in the Compare tool i.e. the "2
changes in..." part which they can take to meetings with the suppliers.

So having looked at the XML of the emf-diff....

Do I just have to look into the "unMatchedElements" section to see the
differences as shown in the top pane e.g.

<unMatchedElements>
<element
href=" file:/D:/Data/Java/workspaces/3.2.2-gash/XMIDiffTest/Advance d%20Trace%20TestBefore1.uml#_E25lUBASEdyBxoipZXxyxg "/>
</unMatchedElements>

i.e. all the subMatchElements I can see appear to have a similarity="1.0"

e.g.

<subMatchElements xsi:type="match:Match2Elements" similarity="1.0">

i.e.

If the element matches then I get a subMatchElements but if not then I
get an unMatchedElements?

If not then were I to write an XSLT which takes an EMF-DIFF file & trys
to generate the top pane as (x)HTML then what should I be looking for?

TIA

Adam

Report message to a moderator

Re: [EMF Compare] Questions wrt EMF-DIFF file [message #88224 is a reply to message #88104]

Thu, 05 July 2007 13:51

Cedric Brun

Messages: 431
Registered: July 2009

Senior Member

Hi Adam,

the emfdiff file is divided in two parts : the match model and the delta
model. The match model link every possible element of one of the version to
the other version, that makes a "Match2Element" . The elements not found in
the other model are described as "UnMatchedElement".

Using this match model the compare engine compute a diff model (or delta
model), basically this diff models says "An element has been added in the
XXX container" or "The element XXX has been moved".

In the emf-diff you'll get both information, the matches and the computed
delta (which correspond to the top pane in the compare tool). Browsing the
diff you should be able to produce your html quite easily.

You can experience a bit, rename an .emfdiff file in a .xmi file, and then
open-it using the reflective editor. You'll see the diff and match part and
you'll be able to browse the model easily.

In XML you should get something like that (as long as you have differences
on your models !)
<diff>
<ownedElements xsi:type="diff:DiffGroup">
<subDiffElements xsi:type="diff:UpdateAttribute">
<attribute
href=" http://www.eclipse.org/emf/2002/GenModel#//GenModel/foreignM odel"/>
<leftElement
href=" file:/D:/dev/workspaces/runtime-New_configuration/library/in puts/genmodel/attributeChange/v1.genmodel#/ "/>
<rightElement
href=" file:/D:/dev/workspaces/runtime-New_configuration/library/in puts/genmodel/attributeChange/v2.genmodel#/ "/>
</subDiffElements>
<subDiffElements xsi:type="diff:UpdateAttribute">
<attribute
href=" http://www.eclipse.org/emf/2002/GenModel#//GenModel/modelNam e"/>
<leftElement
href=" file:/D:/dev/workspaces/runtime-New_configuration/library/in puts/genmodel/attributeChange/v1.genmodel#/ "/>
<rightElement
href=" file:/D:/dev/workspaces/runtime-New_configuration/library/in puts/genmodel/attributeChange/v2.genmodel#/ "/>
</subDiffElements>
</diff>
<match>
<matchedElements xsi:type="match:Match2Elements"
similarity="0.793621867881549">
<subMatchElements xsi:type="match:Match2Elements"
similarity="0.9555555555555557">
<subMatchElements xsi:type="match:Match2Elements" similarity="1.0">
</matchedElements>
</match>

Though I would not encourage you to use XSLT, which is great for XML but can
be tricky for XMI. If the HTML you want to generate is simple, then IMO
Java would do the trick, loading the emf-diff file is easy thanks to EMF,
then you'll be able to browse it in Java. If your generation is a bit more
complicated then I would consider using a M2T transformation tool as
Acceleo or JET for instance.

Cédric

AdamF wrote:

> After some discussion....
>
> All the modelers etc are more than happy with the tool as is but as
> usual....Management want something simple....i.e. an HTML page/Tabular
> view which is basically the top pane in the Compare tool i.e. the "2
> changes in..." part which they can take to meetings with the suppliers.
>
> So having looked at the XML of the emf-diff....
>
> Do I just have to look into the "unMatchedElements" section to see the
> differences as shown in the top pane e.g.
>
>
> <unMatchedElements>
> <element
>
href=" file:/D:/Data/Java/workspaces/3.2.2-gash/XMIDiffTest/Advance d%20Trace%20TestBefore1.uml#_E25lUBASEdyBxoipZXxyxg "/>
> </unMatchedElements>
>
>
> i.e. all the subMatchElements I can see appear to have a similarity="1.0"
>
> e.g.
>
> <subMatchElements xsi:type="match:Match2Elements" similarity="1.0">
>
> i.e.
>
> If the element matches then I get a subMatchElements but if not then I
> get an unMatchedElements?
>
>
> If not then were I to write an XSLT which takes an EMF-DIFF file & trys
> to generate the top pane as (x)HTML then what should I be looking for?
>
>
> TIA
>
> Adam

http://cedric.brun.io news and articles on eclipse and eclipse modeling.

Report message to a moderator

Re: [EMF Compare] Questions wrt EMF-DIFF file [message #88373 is a reply to message #88224]

Fri, 06 July 2007 08:35

Eclipse User

Originally posted by: user.domain.invalid

Cédric Brun wrote:
> Hi Adam,
>
> the emfdiff file is divided in two parts : the match model and the delta
> model. The match model link every possible element of one of the version to
> the other version, that makes a "Match2Element" . The elements not found in
> the other model are described as "UnMatchedElement".
>
> Using this match model the compare engine compute a diff model (or delta
> model), basically this diff models says "An element has been added in the
> XXX container" or "The element XXX has been moved".
>
> In the emf-diff you'll get both information, the matches and the computed
> delta (which correspond to the top pane in the compare tool). Browsing the
> diff you should be able to produce your html quite easily.
>
> You can experience a bit, rename an .emfdiff file in a .xmi file, and then
> open-it using the reflective editor. You'll see the diff and match part and
> you'll be able to browse the model easily.
>
> In XML you should get something like that (as long as you have differences
> on your models !)
> <diff>
> <ownedElements xsi:type="diff:DiffGroup">
> <subDiffElements xsi:type="diff:UpdateAttribute">
> <attribute
> href=" http://www.eclipse.org/emf/2002/GenModel#//GenModel/foreignM odel"/>
> <leftElement
> href=" file:/D:/dev/workspaces/runtime-New_configuration/library/in puts/genmodel/attributeChange/v1.genmodel#/ "/>
> <rightElement
> href=" file:/D:/dev/workspaces/runtime-New_configuration/library/in puts/genmodel/attributeChange/v2.genmodel#/ "/>
> </subDiffElements>
> <subDiffElements xsi:type="diff:UpdateAttribute">
> <attribute
> href=" http://www.eclipse.org/emf/2002/GenModel#//GenModel/modelNam e"/>
> <leftElement
> href=" file:/D:/dev/workspaces/runtime-New_configuration/library/in puts/genmodel/attributeChange/v1.genmodel#/ "/>
> <rightElement
> href=" file:/D:/dev/workspaces/runtime-New_configuration/library/in puts/genmodel/attributeChange/v2.genmodel#/ "/>
> </subDiffElements>
> </diff>
> <match>
> <matchedElements xsi:type="match:Match2Elements"
> similarity="0.793621867881549">
> <subMatchElements xsi:type="match:Match2Elements"
> similarity="0.9555555555555557">
> <subMatchElements xsi:type="match:Match2Elements" similarity="1.0">
> </matchedElements>
> </match>
>
>
> Though I would not encourage you to use XSLT, which is great for XML but can
> be tricky for XMI. If the HTML you want to generate is simple, then IMO
> Java would do the trick, loading the emf-diff file is easy thanks to EMF,
> then you'll be able to browse it in Java. If your generation is a bit more
> complicated then I would consider using a M2T transformation tool as
> Acceleo or JET for instance.
>
>

Oh OK. I had considered that but....

Does your compare plugin allow for extensions etc? i.e. at this stage I
want to have the lightest possible touch upon your code so as to allow
your code to change etc as you move to a version 1 GA etc.

What I was thinking was a simple icon next to the floppy disk icon which
allowed for the generation & then opening of an HTML representation of
the top pane. i.e. whateverYourEmfDiffFileIsCalled.emfdiff >
whateverYourEmfDiffFileIsCalled.html in the same folder.

i.e. I want someone to be able to install the std Compare tool & then
this plugin et voila extra icon etc.

Hopefully if tout est bon then you can integrate my code as a
"management report".

Adam

Report message to a moderator

Re: [EMF Compare] Questions wrt EMF-DIFF file [message #88388 is a reply to message #88373]

Fri, 06 July 2007 10:16

Cedric Brun

Messages: 431
Registered: July 2009

Senior Member

Right now our priority is the three way comparison in order to detect
possible conflicts, we are planning to provide such an extension point but
it's not done yet. Considering our load we will be able to code it around
mid-august but if you want to contribute a patch, do not hesitate: we'll
consider it as fast as possible.

We would like to offer (in a user point of view) a drop-down menu when
clicking on the "export" action. This menu would provide "emfdiff" export
but may provide others depending on the contributions. Each contribution
could be specific to a file extension (some reports only make sense on some
models..). Your "Management Report" would appear here.

Cédric

AdamF wrote:

> Cédric Brun wrote:
>> Hi Adam,
>>
>> the emfdiff file is divided in two parts : the match model and the delta
>> model. The match model link every possible element of one of the version
>> to the other version, that makes a "Match2Element" . The elements not
>> found in the other model are described as "UnMatchedElement".
>>
>> Using this match model the compare engine compute a diff model (or delta
>> model), basically this diff models says "An element has been added in the
>> XXX container" or "The element XXX has been moved".
>>
>> In the emf-diff you'll get both information, the matches and the computed
>> delta (which correspond to the top pane in the compare tool). Browsing
>> the diff you should be able to produce your html quite easily.
>>
>> You can experience a bit, rename an .emfdiff file in a .xmi file, and
>> then open-it using the reflective editor. You'll see the diff and match
>> part and you'll be able to browse the model easily.
>>
>> In XML you should get something like that (as long as you have
>> differences on your models !)
>> <diff>
>> <ownedElements xsi:type="diff:DiffGroup">
>> <subDiffElements xsi:type="diff:UpdateAttribute">
>> <attribute
>> href=" http://www.eclipse.org/emf/2002/GenModel#//GenModel/foreignM odel"/>
>> <leftElement
>>
href=" file:/D:/dev/workspaces/runtime-New_configuration/library/in puts/genmodel/attributeChange/v1.genmodel#/ "/>
>> <rightElement
>>
href=" file:/D:/dev/workspaces/runtime-New_configuration/library/in puts/genmodel/attributeChange/v2.genmodel#/ "/>
>> </subDiffElements>
>> <subDiffElements xsi:type="diff:UpdateAttribute">
>> <attribute
>> href=" http://www.eclipse.org/emf/2002/GenModel#//GenModel/modelNam e"/>
>> <leftElement
>>
href=" file:/D:/dev/workspaces/runtime-New_configuration/library/in puts/genmodel/attributeChange/v1.genmodel#/ "/>
>> <rightElement
>>
href=" file:/D:/dev/workspaces/runtime-New_configuration/library/in puts/genmodel/attributeChange/v2.genmodel#/ "/>
>> </subDiffElements>
>> </diff>
>> <match>
>> <matchedElements xsi:type="match:Match2Elements"
>> similarity="0.793621867881549">
>> <subMatchElements xsi:type="match:Match2Elements"
>> similarity="0.9555555555555557">
>> <subMatchElements xsi:type="match:Match2Elements"
>> similarity="1.0">
>> </matchedElements>
>> </match>
>>
>>
>> Though I would not encourage you to use XSLT, which is great for XML but
>> can
>> be tricky for XMI. If the HTML you want to generate is simple, then IMO
>> Java would do the trick, loading the emf-diff file is easy thanks to EMF,
>> then you'll be able to browse it in Java. If your generation is a bit
>> more complicated then I would consider using a M2T transformation tool as
>> Acceleo or JET for instance.
>>
>>
>
> Oh OK. I had considered that but....
>
> Does your compare plugin allow for extensions etc? i.e. at this stage I
> want to have the lightest possible touch upon your code so as to allow
> your code to change etc as you move to a version 1 GA etc.
>
> What I was thinking was a simple icon next to the floppy disk icon which
> allowed for the generation & then opening of an HTML representation of
> the top pane. i.e. whateverYourEmfDiffFileIsCalled.emfdiff >
> whateverYourEmfDiffFileIsCalled.html in the same folder.
>
>
> i.e. I want someone to be able to install the std Compare tool & then
> this plugin et voila extra icon etc.
>
> Hopefully if tout est bon then you can integrate my code as a
> "management report".
>
> Adam

http://cedric.brun.io news and articles on eclipse and eclipse modeling.

Report message to a moderator