| Summary: | [Transaction Editing Domain] Transaction Editing domain id needs to be registered and change | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Arthur Daussy <arthur.daussy> | ||||||||||
| Component: | Core | Assignee: | Arthur Daussy <arthur.daussy> | ||||||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||||||
| Severity: | enhancement | ||||||||||||
| Priority: | P3 | CC: | alain.leguennec, cedric.dumoulin, faure.tristan | ||||||||||
| Version: | 0.8.1 | ||||||||||||
| Target Milestone: | --- | ||||||||||||
| Hardware: | All | ||||||||||||
| OS: | All | ||||||||||||
| Whiteboard: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Arthur Daussy
Created attachment 207912 [details]
Correction for Transaction Editing Domain
Correction for transaction Editing Domain
Created attachment 207928 [details]
New correction
New correction with observation from dev list.
Committed on the 0.8.X branch. Will be backported soon.. Just a quick question: I have not seen any de-registration. Won't the registration cause a leak? Yes the registration is here: TransactionalEditingDomain.Registry.INSTANCE.add(PAPYRUS_EDITING_DOMAIN_ID, transactionalEditingDomain); However Cedric raise another problem (see email in attachment) that is a real problem when multiple papyrus editor are open. I am currently looking into it. Let you know when I have found a better solution. Created attachment 208044 [details]
Email from Cedric Dumoulin on mailing list
Exchange on mailing list
Hi,
The main problem with no registration of the editing domain is you can not use the extension point of EMF transaction to register listener easily:
org.eclipse.emf.transaction.listeners
As creation of the Papyrus Editing Domain is hand made ( see org.eclipse.papyrus.resource.ModelSet)we have integrate this mechanism into MDT Papyrus. With this solution Papyrus transactional editing domain will not need to be registered.
However we have not been able to find where the Transactional Editing domain was dispose. So as Alain said, it still may persist some leak. Cedric do you have any idea on this topic. If none, I will start a discussion about it on the dev list.
Regards.
Created attachment 208047 [details]
New correction
Committed on trunk and branch 0.8.x. |