Community
Participate
Working Groups
It is a general pb with a category of discoverers which does not serialize the resulting models : - Generic XML Model Discoverer - EjbJar XML Model Discoverer - WebApp XML Discoverer When called from the popup menu on a file, the discovery itself is ok but the model openening in modisco browser reinstantiate the model from the "XX.xml" file which leads to call another EMF Resource Factory -> the model finally opened does not conform to the mm asked. This pb does not occurs with other discoverers which produces a .xmi result file. This side effect is not visible in 0.8 since only 'Generic XML discoverer' was included.
This problem has to be resolved within the MoDisco Discovery Framework refactoring task which is currently in progress.
a reminder : not sure of the reason why a wrong Resource Factory is used by the Modisco Browser : the code used to force the good factory in global Resource.FActory registry. It used to work. Whatever the problem is, the good solution is to give the instanciated resource directly to the MoDisco browser -> MoDisco Discovery Framework refactoring task.
Completing last comment : "the code used to force the good factory in global Resource.FActory registry. It used to work." The problem comes now from MoDisco Model browser which evolves with some asynchronous model opening (to avoid UI freez i think) -> the workaround "force the good factory in global Resource.FActory registry" does not work anymore. For instance : taking a "web.webapp25" file, and launching a "discover generic xml" results in opening a webapp25 model rather than a xml model.
Fixed the three discvoerers (XML, JEE webapp and ejbjar discoverer) for sending directly the result Resource to the MoDisco browser (rev 3629).
Bug fixed.
