Hi Jonatan,
The list is calculated when getConnectorsWithOwnedPorts() is called.
This discussion makes me to reflect about the aim of my approach.
And now I have another idea about what the information I want retrieve easily:
“what is the port(s)/portRole(s) connected which to a specify port/portRole?”
I think that this information is very useful. And without it, PortRole is not sense of exist.
Because, for me, the idea of PortRole is for each part of a block its ports play differently (it’s means,
connect to different ports according to various contexts). With PortRole we can define each role played
by a port in a specify context and consequently each PortRole needs know to which port(s)/portRole(s)
it is connected.
What do you think?
Thanks
Yupanqui
De : esf-dev-bounces@xxxxxxxxxxxx
[mailto:esf-dev-bounces@xxxxxxxxxxxx] De la part de Jonathan DUMONT
Envoyé : vendredi 17 avril 2015 10:59
À : esf-dev@xxxxxxxxxxxx
Objet : Re: [esf-dev] Work about ESF Metamodel
Hi all !
What I wanted to explain is that using a property, derived or not, to ensure that an architectural element, which owns ports, knows the links associated to these ports imply to maintain the list on each modifications, etc. That's what I meant by costly.
It can be interesting to have this link but I think that this complexity can be pushed on the code side, not in the metamodel.
Regards,
Jonathan
Le 17/04/2015 10:40, MUNOZ JULHO Yupanqui a écrit :
Hi everybody,
Matthieu, I just submitted.
The result of the meeting is work on the metamodel. 21/04, Jonathan will be here whole day. Everybody is invited to joins us this day for working. =)
Jonathan, why is it costly?
“An architectural element doesn't know directly the connectors linked to the ports that it owns. This can be a derived property ... but it costs a lot to maintain.”
Yupanqui
Hi Yupanqui,
Do you push last modification we talk about this afternoon ?
What was the result of the meeting with Jonathan ?
Have a nice (summer) day
J
Hi everybody,
In this path “SVN\Trunk\Documentation\Metamodel\” you can find “org.polarsys.esf.core.metamodel.proto”.
That project contents the metamodel and the specification for metamodel.
Please, think of :
-
leaving the comments (to explain modifications);
-
updating frequently (for getting the latest metamodel);
-
committing regularly (not take so long) .
Thanks!
Yupanqui
_______________________________________________
esf-dev mailing list
esf-dev@xxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://polarsys.org/mailman/listinfo/esf-dev
