Community
Participate
Working Groups
The local customization are stored in the fields localCustomization AND in customizations. Sometimes, the save action is not correctly done -> when we re-open the table, the local customizations are not applied. To get this bad state, we need to apply "external" customization on the table. Step to reproduce the bugs : 1/Create a table 2/Apply a customization on the table 3/Save and close the table 4/Open the table -> in the Load Customization Dialog, you can see that the local customizations are unloaded! If we open the table in text mode, we notice that the path for local customizations is not correct : <customizations href="/testTable/withTable.table#//@localCustomizations.0"/> <customizations href="/testTable/withTable.table#//@localCustomizations.1"/> <customizations href="emffacet:/customization/testCustomization#/"/> instead of <customizations href="#//@localCustomizations.0"/> <customizations href="#//@localCustomizations.1"/> <customizations href="emffacet:/customization/testCustomization#/"/> FYI, if you do : 1/Create a table 2/Save and close the table 3/Open an Apply a customization on the table 4/Save the table 5/Open the table -> you don't have the problem 6/ if you "Save As" your table -> you get bad paths for the local customizations
Created attachment 194142 [details] This patch adds asserts which allow to prove the bug. It doesn't resolve it! (1) I, Vincent Lorenzo, wrote 100% of the code I've provided. (2) This code contains no cryptography (3) I have the right to contribute the code to Eclipse. (4) I contribute the content under the EPL.
Comment on attachment 194142 [details] This patch adds asserts which allow to prove the bug. It doesn't resolve it! Here is a patch smaller that 250 lines (32 lines), no CQ is then needed. I've committed this patch. Committed revision 639.
I've fixed this bug by using "URI.createPlatformResourceURI" instead of "URI.createFileURI" to avoid XMI serialization problems. Regards, Gregoire Dupe
This bug can be marked as closed
