Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Voicetools » Orphaned connector (cross post)
Orphaned connector (cross post) [message #22804] Sat, 04 July 2009 22:24 Go to next message
No real name is currently offline No real nameFriend
Messages: 11
Registered: July 2009
Junior Member
Hi I've imported a war file which contains several projects, 3
calldesign.xml files and 2 calldesign.frag.

I can open every file except one of the calldesign.frag files. I get an
orphaned connector error.

Any idea what this could be or where I could start looking? I've spent
several hours on this. I've checked out this news group and did some
googling to no avail. Here's the full Exception:

java.lang.RuntimeException: orphaned connector:
id=d13df3d457844dbaaac5b85966a47601
origin=c0e75e56c8804d559666f7a953d839a6
destination=aae216cd474b45c99cdfdd63b1fb0ad7
at org.eclipse.vtp.desktop.model.core.Connector.<init>(Connector.java:53)
at org.eclipse.vtp.desktop.model.core.Model.<init>(Model.java:102)
at
org.eclipse.vtp.desktop.editors.core.impl.ApplicationFragmen tEditor.init(ApplicationFragmentEditor.java:198)
at org.eclipse.ui.internal.EditorManager.createSite(EditorManag er.java:794)
at
org.eclipse.ui.internal.EditorReference.createPartHelper(Edi torReference.java:643)
at
org.eclipse.ui.internal.EditorReference.createPart(EditorRef erence.java:426)
at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(Workb enchPartReference.java:592)
at
org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(Ed itorAreaHelper.java:263)
at
org.eclipse.ui.internal.EditorManager.setVisibleEditor(Edito rManager.java:1405)
at
org.eclipse.ui.internal.EditorManager$5.runWithException(Edi torManager.java:939)
at
org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.java:31)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:129)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3659)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3296)
at
org.eclipse.ui.application.WorkbenchAdvisor.openWindows(Work benchAdvisor.java:801)
at
org.eclipse.ui.internal.Workbench$25.runWithException(Workbe nch.java:1342)
at
org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.java:31)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:129)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3659)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3296)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2309)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 19)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:289)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:106)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:76)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:363)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
Re: Orphaned connector (cross post) [message #22854 is a reply to message #22804] Wed, 08 July 2009 19:43 Go to previous messageGo to next message
Randy Childers is currently offline Randy ChildersFriend
Messages: 121
Registered: July 2009
Senior Member
Replied directly, as this contains project-specific information.

However, for posterity and all that, know that this error happens when the
callflow references some specific custom component which isn't currently
present in the OpenVXML installation. For example, an integration that
makes some sort of specific webservice or database query which was coded in
its own custom module.

Randy Childers
OpenMethods


On 7/4/09 5:24 PM, in article
57544be29357d70190cb67398a012671$1@www.eclipse.org, "Cam"
<cmcdonough@enmax.com> wrote:

> Hi I've imported a war file which contains several projects, 3
> calldesign.xml files and 2 calldesign.frag.
>
> I can open every file except one of the calldesign.frag files. I get an
> orphaned connector error.
>
> Any idea what this could be or where I could start looking? I've spent
> several hours on this. I've checked out this news group and did some
> googling to no avail. Here's the full Exception:
>
> java.lang.RuntimeException: orphaned connector:
> id=d13df3d457844dbaaac5b85966a47601
> origin=c0e75e56c8804d559666f7a953d839a6
> destination=aae216cd474b45c99cdfdd63b1fb0ad7
> at org.eclipse.vtp.desktop.model.core.Connector.<init>(Connector.java:53)
> at org.eclipse.vtp.desktop.model.core.Model.<init>(Model.java:102)
> at
> org.eclipse.vtp.desktop.editors.core.impl.ApplicationFragmen tEditor.init(Appli
> cationFragmentEditor.java:198)
> at org.eclipse.ui.internal.EditorManager.createSite(EditorManag er.java:794)
> at
> org.eclipse.ui.internal.EditorReference.createPartHelper(Edi torReference.java:
> 643)
> at
> org.eclipse.ui.internal.EditorReference.createPart(EditorRef erence.java:426)
> at
> org.eclipse.ui.internal.WorkbenchPartReference.getPart(Workb enchPartReference.
> java:592)
> at
> org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(Ed itorAreaHelper.jav
> a:263)
> at
>
org.eclipse.ui.internal.EditorManager.setVisibleEditor(Edito rManager.java:1405 >
)
> at
> org.eclipse.ui.internal.EditorManager$5.runWithException(Edi torManager.java:93
> 9)
> at
> org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.
> java:31)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:129)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3659)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3296)
> at
> org.eclipse.ui.application.WorkbenchAdvisor.openWindows(Work benchAdvisor.java:
> 801)
> at
> org.eclipse.ui.internal.Workbench$25.runWithException(Workbe nch.java:1342)
> at
> org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.
> java:31)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:129)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3659)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3296)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2309)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 19)
> at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:289)
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:461)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
> at
> org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.ja
> va:106)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:16
> 9)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(Ec
> lipseAppLauncher.java:106)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppL
> auncher.java:76)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:363)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:176)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 508)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
>
Re: Orphaned connector (cross post) [message #22898 is a reply to message #22854] Wed, 08 July 2009 20:55 Go to previous messageGo to next message
No real name is currently offline No real nameFriend
Messages: 11
Registered: July 2009
Junior Member
Thanks Randy.

The problem was that the there were in essense plugins or modules missing.
One specific plugin being used included a date in it's naming convention.
The date of the plug-in loaded into eclipse 'drop-in' directory was in
conflict with the date of the plug-in referenced within the rest of the
application.
Re: Orphaned connector (cross post) [message #22942 is a reply to message #22854] Wed, 08 July 2009 21:05 Go to previous message
No real name is currently offline No real nameFriend
Messages: 11
Registered: July 2009
Junior Member
Thanks Randy,

You indicated pretty much what the problem was. A specific plug-in that
was used in this application referenced several other plug-ins that used a
naming convention that included the date. A conflict arised between the
file name *20080618*.* and another one *20080807*.*. Basically the
application was searching for a module that wasn't there, in that a newer
version was being referenced in parts of the app.

Appreciate the help :)
Re: Orphaned connector (cross post) [message #578612 is a reply to message #22804] Wed, 08 July 2009 19:43 Go to previous message
Randy Childers is currently offline Randy ChildersFriend
Messages: 121
Registered: July 2009
Senior Member
Replied directly, as this contains project-specific information.

However, for posterity and all that, know that this error happens when the
callflow references some specific custom component which isn't currently
present in the OpenVXML installation. For example, an integration that
makes some sort of specific webservice or database query which was coded in
its own custom module.

Randy Childers
OpenMethods


On 7/4/09 5:24 PM, in article
57544be29357d70190cb67398a012671$1@www.eclipse.org, "Cam"
<cmcdonough@enmax.com> wrote:

> Hi I've imported a war file which contains several projects, 3
> calldesign.xml files and 2 calldesign.frag.
>
> I can open every file except one of the calldesign.frag files. I get an
> orphaned connector error.
>
> Any idea what this could be or where I could start looking? I've spent
> several hours on this. I've checked out this news group and did some
> googling to no avail. Here's the full Exception:
>
> java.lang.RuntimeException: orphaned connector:
> id=d13df3d457844dbaaac5b85966a47601
> origin=c0e75e56c8804d559666f7a953d839a6
> destination=aae216cd474b45c99cdfdd63b1fb0ad7
> at org.eclipse.vtp.desktop.model.core.Connector.<init>(Connector.java:53)
> at org.eclipse.vtp.desktop.model.core.Model.<init>(Model.java:102)
> at
> org.eclipse.vtp.desktop.editors.core.impl.ApplicationFragmen tEditor.init(Appli
> cationFragmentEditor.java:198)
> at org.eclipse.ui.internal.EditorManager.createSite(EditorManag er.java:794)
> at
> org.eclipse.ui.internal.EditorReference.createPartHelper(Edi torReference.java:
> 643)
> at
> org.eclipse.ui.internal.EditorReference.createPart(EditorRef erence.java:426)
> at
> org.eclipse.ui.internal.WorkbenchPartReference.getPart(Workb enchPartReference.
> java:592)
> at
> org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(Ed itorAreaHelper.jav
> a:263)
> at
>
org.eclipse.ui.internal.EditorManager.setVisibleEditor(Edito rManager.java:1405 >
)
> at
> org.eclipse.ui.internal.EditorManager$5.runWithException(Edi torManager.java:93
> 9)
> at
> org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.
> java:31)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:129)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3659)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3296)
> at
> org.eclipse.ui.application.WorkbenchAdvisor.openWindows(Work benchAdvisor.java:
> 801)
> at
> org.eclipse.ui.internal.Workbench$25.runWithException(Workbe nch.java:1342)
> at
> org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.
> java:31)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:129)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3659)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3296)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2309)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 19)
> at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:289)
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:461)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
> at
> org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.ja
> va:106)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:16
> 9)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(Ec
> lipseAppLauncher.java:106)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppL
> auncher.java:76)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:363)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:176)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 508)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
>
Re: Orphaned connector (cross post) [message #578625 is a reply to message #22854] Wed, 08 July 2009 20:55 Go to previous message
No real name is currently offline No real nameFriend
Messages: 11
Registered: July 2009
Junior Member
Thanks Randy.

The problem was that the there were in essense plugins or modules missing.
One specific plugin being used included a date in it's naming convention.
The date of the plug-in loaded into eclipse 'drop-in' directory was in
conflict with the date of the plug-in referenced within the rest of the
application.
Re: Orphaned connector (cross post) [message #578638 is a reply to message #22854] Wed, 08 July 2009 21:05 Go to previous message
No real name is currently offline No real nameFriend
Messages: 11
Registered: July 2009
Junior Member
Thanks Randy,

You indicated pretty much what the problem was. A specific plug-in that
was used in this application referenced several other plug-ins that used a
naming convention that included the date. A conflict arised between the
file name *20080618*.* and another one *20080807*.*. Basically the
application was searching for a module that wasn't there, in that a newer
version was being referenced in parts of the app.

Appreciate the help :)
Previous Topic:Orphaned connector (cross post)
Next Topic:Usage of DATETIME object
Goto Forum:
  


Current Time: Sun Dec 21 10:12:31 GMT 2014

Powered by FUDForum. Page generated in 0.02309 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software