- This topic has 1 reply, 2 voices, and was last updated 13 years, 1 month ago by
.
-
Posts
-
We have ported our WebSphere Development Studio Client for iSeries Enterprise Java application over to myeclipse blue. We have web services in this project and are adding a new one. We noticed when moving the workspace into MEB, that it was best to NOT INCLUDE the .xmi files. They seemed to not be read properly or something – the project was rather unusable. Since, I have created a new web service in the tool and have therfore generated .xmi files for it. If I regenerate the older service I will produce .xmi files for that service as well. Should I?
What is the official word on these .xmi files? Is it known to not bring those in from a project such as ours? Is it recommended they all be regenerated. Can each developer then share those .xmi files or should they recreate them? Any info on this is appreciated.
James
Jim,
We don’t have a official position on web services .xmi files and aren’t aware of a problem with them for migrated projects. Could you give some more details about the problems you had when migrating a workspace with the XMI files, including how you generated the .xmi files? It’s not clear what you mean by “unstable”.
If you are concerned about regenerating the older service, I suggest taking a backup of the workspace and then trying.
