CODEWITHSUNDEEP
migrationibm-mobilefirstmobilefirst-studio
Nataliya Le Loup
Nataliya Le Loup

Reputation: 125

Migration to MobileFirst

I do migration of worklight projects to mobilefirst. When I open project created in worklight version 6.2 in new mobilefirst studio I see this project always as closed in eclipse. When I try to open it then I get this error:

!ENTRY com.worklight.studio.plugin 4 0 2015-02-17 13:09:10.550
!MESSAGE FWLPL0019E: Migrating the HiPerForms project from version     6.2.0.01.20141002-2218 to version 6.3.0.00.20141127-1357 has failed because     org.w3c.dom.DOMException: NOT_FOUND_ERR: An attempt is made to reference a node in a context where it does not exist.; FWLPL0019E: Migrating the HiPerForms project from version 6.2.0.01.20141002-2218 to version 6.3.0.00.20141127-1357 has failed because org.w3c.dom.DOMException: NOT_FOUND_ERR: An attempt is made to reference a node in a context where it does not exist.
!STACK 0 com.worklight.upgrader.UpgradeEngineException: FWLPL0019E: Migrating the HiPerForms project from version 6.2.0.01.20141002-2218 to version 6.3.0.00.20141127-1357 has failed because org.w3c.dom.DOMException: NOT_FOUND_ERR: An attempt is made to reference a node in a context where it does not exist.
at com.worklight.upgrader.WLUpgradeEngine.upgradeProject(WLUpgradeEngine.java:271)
at com.worklight.studio.plugin.upgrader.WLUpgraderWorkspaceJob.runInWorkspace(Unknown Source)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

When I delete .settings folder of the project I can open the project in eclipse but then after restarting eclipse I have again closed project.

Any idea what's it could be? Thank you for help!

Upvotes: 0

Views: 248

Answers (1)

Idan Adar
Idan Adar

Reputation: 44516

As this is likely a migration error and since you cannot provide the project's source code here, my suggestion for you is to open an IBM support ticket (PMR) and provide your source code there so that the bug could be debugged and resolved.

Edit: a smaller project was provided in the comments to this answer. The error was reproduced and the bug was found and will be fixed. See below for a workaround. You can open a PMR in order to receive a fixed Studio build.

Workaround
To workaround it, remove the proxy node from adapter XML file and try to migrate. Then, add it back after migration completes.

Upvotes: 1

Related Questions