Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Transaction Editing Domain ID

  Hi,

  Do you speak of registering it in the Eclipse Registry ?
  What is the added value of registering the EditingDomain ?
  How do you enable several Papyrus EditingDomain (one per Papyrus instance) ?

  If I remember well, The EditingDomain is associated to the ResourceSet, so to the models (uml, notations, ...).

  It is not registered intentionally, because there is one EditingDomain per Papyrus instance (each Papyrus instance edit one uml model).
  In Papyrus, the EditingDomain is shared, but only between the same nested diagrams and views of one Papyrus instance.
  It should not be shared between several instances of Papyrus.

  Does the registering mechanism allow to register one EditingDomain per Papyrus instance ? I don't think that as there is only one ID.
  
  So my point of view is that the EditingDomain should not be registered in Eclipse registry. The right way to get the EditingDomain in Papyrus is to get it from the Papyrus ServiceRegistry.

   Cedric


DAUSSY Arthur a écrit :

Hi everyone,

 

 I would like to highlight the following bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=365577.

 For now the current Transactional Editing Domain is never register in the Transactional Editing Domain registry. So this bug will solve this issue.

 However I would like to change the id which is at the moment “SharedEditingDomain” which maybe a bit simple to be used as ID for "org.eclipse.papyrus.SharedEditingDomain".

 So I would like to have validation from the community before changing it (to be sure nobody use somewhere else the string “SharedEditingDomain”).

 

Regards,

 

Arthur daussy

Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos ne pourra être engagée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être engagée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.



_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

Back to the top