Home » Archived » BPMN Modeler » Problems when connecting two elements
Problems when connecting two elements [message #9423] |
Sat, 28 February 2009 23:42 |
Rômulo rpini Messages: 36 Registered: July 2009 |
Member |
|
|
Hi all,
I am still a begginner on Eclipse, ok. Then I downloaded Eclise SDK 3.4.0.
I wanted to use the BMPM modeler, so I went to software update, typed BPMN
and installed 'bpmn project feature'. So I created a project and then a
bpmn diagram. But when I try to use a flow connector between two elements
(process, gateways, and so on) the editor crashes and I get several errors
in the log. And then it stays like this:
http://img178.imageshack.us/img178/9817/bugb.jpg
Yeah, exactly like that. Every time I try the arrow stays on the top left.
I've tried everything. Downloaded again, installed every stp component,
but no success at all.
Anyone here know how to solve this? : (
Best Regards,
RÃŽmulo Arpini
|
|
|
Re: Problems when connecting two elements [message #9447 is a reply to message #9423] |
Sun, 01 March 2009 16:02 |
Rômulo rpini Messages: 36 Registered: July 2009 |
Member |
|
|
Here is the log anyway...
!SESSION 2009-03-01 12:58:43.000
-----------------------------------------------
eclipse.buildId=I20080617-2000
java.version=1.6.0_12
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pt_BR
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.gmf.runtime.diagram.ui 4 4 2009-03-01 12:59:43.140
!MESSAGE execute
!STACK 0
org.eclipse.core.commands.ExecutionException: While executing the
operation, an exception occurred
at
org.eclipse.core.commands.operations.DefaultOperationHistory .execute(DefaultOperationHistory.java:519)
at
org.eclipse.gmf.runtime.diagram.ui.parts.DiagramCommandStack .execute(DiagramCommandStack.java:205)
at
org.eclipse.gmf.runtime.diagram.ui.parts.DiagramCommandStack .execute(DiagramCommandStack.java:168)
at
org.eclipse.gmf.runtime.diagram.ui.parts.DiagramCommandStack .execute(DiagramCommandStack.java:155)
at
org.eclipse.gef.tools.AbstractTool.executeCommand(AbstractTo ol.java:399)
at
org.eclipse.gef.tools.AbstractTool.executeCurrentCommand(Abs tractTool.java:411)
at
org.eclipse.gmf.runtime.diagram.ui.tools.ConnectionCreationT ool.handleCreateConnection(ConnectionCreationTool.java:341)
at
org.eclipse.gmf.runtime.diagram.ui.tools.ConnectionCreationT ool.handleButtonUp(ConnectionCreationTool.java:181)
at
org.eclipse.gmf.runtime.diagram.ui.internal.tools.Connection HandleTool.handleButtonUp(ConnectionHandleTool.java:132)
at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java :1064)
at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.ja va:544)
at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:263)
at
org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouse Released(DomainEventDispatcher.java:374)
at
org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(Li ghtweightSystem.java:538)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:207)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3422)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
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: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: java.lang.IllegalArgumentException: Corrupted model
org.eclipse.stp.bpmn.impl.ActivityImpl@1f4ea9d (iD:
_9WipIAZ5Ed6RlLs5UGMkXQ) (documentation: null, name: null, ncname: null,
orderedMessages: [], activityType: <unset>, looping: <unset>)
at
org.eclipse.stp.bpmn.diagram.edit.parts.ActivityEditPart.ref reshTargetConnections(ActivityEditPart.java:650)
at
org.eclipse.gmf.runtime.diagram.ui.editparts.ShapeNodeEditPa rt.handleNotificationEvent(ShapeNodeEditPart.java:229)
at
org.eclipse.stp.bpmn.diagram.edit.parts.ActivityEditPart.han dleNotificationEvent(ActivityEditPart.java:625)
at
org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPa rt.notifyChanged(GraphicalEditPart.java:1414)
at
org.eclipse.gmf.runtime.diagram.core.listener.DiagramEventBr oker.fireNotification(DiagramEventBroker.java:500)
at
org.eclipse.gmf.runtime.diagram.core.listener.DiagramEventBr oker.resourceSetChanged(DiagramEventBroker.java:395)
at
org.eclipse.gmf.runtime.diagram.ui.internal.DiagramEventBrok erThreadSafe.resourceSetChanged(DiagramEventBrokerThreadSafe .java:72)
at
org.eclipse.gmf.runtime.diagram.core.DiagramEditingDomainFac tory$DiagramEditingDomain.postcommit(DiagramEditingDomainFac tory.java:213)
at
org.eclipse.emf.transaction.impl.TransactionalEditingDomainI mpl.deactivate(TransactionalEditingDomainImpl.java:504)
at
org.eclipse.emf.transaction.impl.TransactionImpl.close(Trans actionImpl.java:623)
at
org.eclipse.emf.transaction.impl.TransactionImpl.commit(Tran sactionImpl.java:415)
at
org.eclipse.emf.workspace.AbstractEMFOperation.execute(Abstr actEMFOperation.java:172)
at
org.eclipse.gmf.runtime.common.core.command.CompositeCommand .doExecuteWithResult(CompositeCommand.java:403)
at
org.eclipse.gmf.runtime.common.core.command.AbstractCommand. execute(AbstractCommand.java:135)
at
org.eclipse.gmf.runtime.common.core.command.CompositeCommand .doExecuteWithResult(CompositeCommand.java:403)
at
org.eclipse.gmf.runtime.common.core.command.AbstractCommand. execute(AbstractCommand.java:135)
at
org.eclipse.gmf.runtime.common.core.command.CompositeCommand .doExecuteWithResult(CompositeCommand.java:403)
at
org.eclipse.gmf.runtime.common.core.command.AbstractCommand. execute(AbstractCommand.java:135)
at
org.eclipse.core.commands.operations.DefaultOperationHistory .execute(DefaultOperationHistory.java:511)
... 38 more
Caused by: java.lang.NullPointerException
at
org.eclipse.gmf.runtime.draw2d.ui.figures.BaseSlidableAnchor .hashCode(BaseSlidableAnchor.java:137)
at java.util.HashMap.put(Unknown Source)
at java.util.HashSet.add(Unknown Source)
at
org.eclipse.stp.bpmn.figures.connectionanchors.impl.ModelAwa reAnchor.addAnchorListener(ModelAwareAnchor.java:240)
at
org.eclipse.draw2d.PolylineConnection.hookSourceAnchor(Polyl ineConnection.java:155)
at
org.eclipse.draw2d.PolylineConnection.setSourceAnchor(Polyli neConnection.java:261)
at
org.eclipse.gef.editparts.AbstractConnectionEditPart.refresh SourceAnchor(AbstractConnectionEditPart.java:229)
at
org.eclipse.gef.editparts.AbstractConnectionEditPart.refresh (AbstractConnectionEditPart.java:219)
at
org.eclipse.gmf.runtime.diagram.ui.editparts.ConnectionEditP art.access$1(ConnectionEditPart.java:1)
at
org.eclipse.gmf.runtime.diagram.ui.editparts.ConnectionEditP art$5.run(ConnectionEditPart.java:1122)
at
org.eclipse.emf.transaction.impl.TransactionalEditingDomainI mpl.runExclusive(TransactionalEditingDomainImpl.java:289)
at
org.eclipse.gmf.runtime.diagram.ui.editparts.ConnectionEditP art.refresh(ConnectionEditPart.java:1119)
at
org.eclipse.gef.editparts.AbstractConnectionEditPart.setTarg et(AbstractConnectionEditPart.java:295)
at
org.eclipse.gef.editparts.AbstractGraphicalEditPart.addTarge tConnection(AbstractGraphicalEditPart.java:278)
at
org.eclipse.gef.editparts.AbstractGraphicalEditPart.refreshT argetConnections(AbstractGraphicalEditPart.java:674)
at
org.eclipse.stp.bpmn.diagram.edit.parts.ActivityEditPart.ref reshTargetConnections(ActivityEditPart.java:645)
... 56 more
!ENTRY org.eclipse.ui 4 0 2009-03-01 12:59:43.171
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable
(java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:3777)
at org.eclipse.swt.SWT.error(SWT.java:3695)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3800)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3425)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
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: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: java.lang.NullPointerException
at
org.eclipse.draw2d.RelativeBendpoint.getLocation(RelativeBen dpoint.java:63)
at
org.eclipse.gmf.runtime.diagram.ui.editparts.ShapeCompartmen tEditPart$ConnectionRefreshMgr.refreshConnections(ShapeCompa rtmentEditPart.java:165)
at
org.eclipse.gmf.runtime.diagram.ui.editparts.ShapeCompartmen tEditPart.forceRefreshConnections(ShapeCompartmentEditPart.j ava:612)
at
org.eclipse.gmf.runtime.diagram.ui.editparts.ShapeCompartmen tEditPart$2.run(ShapeCompartmentEditPart.java:595)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:133)
... 22 more
Best Regards,
Romulo Arpini
|
|
|
Re: Problems when connecting two elements [message #9470 is a reply to message #9447] |
Sun, 01 March 2009 16:48 |
Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
This is most likely fixed in trunk and you can try it out with the STP
update site for Galileo.
It is most likely that your model is corrupted and the edge doesn't know
where to place itself on its owner, thus throwing a NPE.
If you can reproduce the problem by drawing a diagram in some
reproducible way, please open a bug about it.
Thanks,
Antoine
Rômulo Arpini wrote:
> Here is the log anyway...
> !SESSION 2009-03-01 12:58:43.000
> -----------------------------------------------
> eclipse.buildId=I20080617-2000
> java.version=1.6.0_12
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pt_BR
> Command-line arguments: -os win32 -ws win32 -arch x86
>
> !ENTRY org.eclipse.gmf.runtime.diagram.ui 4 4 2009-03-01 12:59:43.140
> !MESSAGE execute
> !STACK 0
> org.eclipse.core.commands.ExecutionException: While executing the
> operation, an exception occurred
> at
> org.eclipse.core.commands.operations.DefaultOperationHistory .execute(DefaultOperationHistory.java:519)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.parts.DiagramCommandStack .execute(DiagramCommandStack.java:205)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.parts.DiagramCommandStack .execute(DiagramCommandStack.java:168)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.parts.DiagramCommandStack .execute(DiagramCommandStack.java:155)
>
> at org.eclipse.gef.tools.AbstractTool.executeCommand(AbstractTo ol.java:399)
> at
> org.eclipse.gef.tools.AbstractTool.executeCurrentCommand(Abs tractTool.java:411)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.tools.ConnectionCreationT ool.handleCreateConnection(ConnectionCreationTool.java:341)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.tools.ConnectionCreationT ool.handleButtonUp(ConnectionCreationTool.java:181)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.internal.tools.Connection HandleTool.handleButtonUp(ConnectionHandleTool.java:132)
>
> at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java :1064)
> at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.ja va:544)
> at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:263)
> at
> org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouse Released(DomainEventDispatcher.java:374)
>
> at
> org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(Li ghtweightSystem.java:538)
>
> at
> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:207)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3823)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3422)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
>
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
> at
> org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
>
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>
> 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: 549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> Caused by: java.lang.IllegalArgumentException: Corrupted model
> org.eclipse.stp.bpmn.impl.ActivityImpl@1f4ea9d (iD:
> _9WipIAZ5Ed6RlLs5UGMkXQ) (documentation: null, name: null, ncname: null,
> orderedMessages: [], activityType: <unset>, looping: <unset>)
> at
> org.eclipse.stp.bpmn.diagram.edit.parts.ActivityEditPart.ref reshTargetConnections(ActivityEditPart.java:650)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.editparts.ShapeNodeEditPa rt.handleNotificationEvent(ShapeNodeEditPart.java:229)
>
> at
> org.eclipse.stp.bpmn.diagram.edit.parts.ActivityEditPart.han dleNotificationEvent(ActivityEditPart.java:625)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPa rt.notifyChanged(GraphicalEditPart.java:1414)
>
> at
> org.eclipse.gmf.runtime.diagram.core.listener.DiagramEventBr oker.fireNotification(DiagramEventBroker.java:500)
>
> at
> org.eclipse.gmf.runtime.diagram.core.listener.DiagramEventBr oker.resourceSetChanged(DiagramEventBroker.java:395)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.internal.DiagramEventBrok erThreadSafe.resourceSetChanged(DiagramEventBrokerThreadSafe .java:72)
>
> at
> org.eclipse.gmf.runtime.diagram.core.DiagramEditingDomainFac tory$DiagramEditingDomain.postcommit(DiagramEditingDomainFac tory.java:213)
>
> at
> org.eclipse.emf.transaction.impl.TransactionalEditingDomainI mpl.deactivate(TransactionalEditingDomainImpl.java:504)
>
> at
> org.eclipse.emf.transaction.impl.TransactionImpl.close(Trans actionImpl.java:623)
>
> at
> org.eclipse.emf.transaction.impl.TransactionImpl.commit(Tran sactionImpl.java:415)
>
> at
> org.eclipse.emf.workspace.AbstractEMFOperation.execute(Abstr actEMFOperation.java:172)
>
> at
> org.eclipse.gmf.runtime.common.core.command.CompositeCommand .doExecuteWithResult(CompositeCommand.java:403)
>
> at
> org.eclipse.gmf.runtime.common.core.command.AbstractCommand. execute(AbstractCommand.java:135)
>
> at
> org.eclipse.gmf.runtime.common.core.command.CompositeCommand .doExecuteWithResult(CompositeCommand.java:403)
>
> at
> org.eclipse.gmf.runtime.common.core.command.AbstractCommand. execute(AbstractCommand.java:135)
>
> at
> org.eclipse.gmf.runtime.common.core.command.CompositeCommand .doExecuteWithResult(CompositeCommand.java:403)
>
> at
> org.eclipse.gmf.runtime.common.core.command.AbstractCommand. execute(AbstractCommand.java:135)
>
> at
> org.eclipse.core.commands.operations.DefaultOperationHistory .execute(DefaultOperationHistory.java:511)
>
> ... 38 more
> Caused by: java.lang.NullPointerException
> at
> org.eclipse.gmf.runtime.draw2d.ui.figures.BaseSlidableAnchor .hashCode(BaseSlidableAnchor.java:137)
>
> at java.util.HashMap.put(Unknown Source)
> at java.util.HashSet.add(Unknown Source)
> at
> org.eclipse.stp.bpmn.figures.connectionanchors.impl.ModelAwa reAnchor.addAnchorListener(ModelAwareAnchor.java:240)
>
> at
> org.eclipse.draw2d.PolylineConnection.hookSourceAnchor(Polyl ineConnection.java:155)
>
> at
> org.eclipse.draw2d.PolylineConnection.setSourceAnchor(Polyli neConnection.java:261)
>
> at
> org.eclipse.gef.editparts.AbstractConnectionEditPart.refresh SourceAnchor(AbstractConnectionEditPart.java:229)
>
> at
> org.eclipse.gef.editparts.AbstractConnectionEditPart.refresh (AbstractConnectionEditPart.java:219)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.editparts.ConnectionEditP art.access$1(ConnectionEditPart.java:1)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.editparts.ConnectionEditP art$5.run(ConnectionEditPart.java:1122)
>
> at
> org.eclipse.emf.transaction.impl.TransactionalEditingDomainI mpl.runExclusive(TransactionalEditingDomainImpl.java:289)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.editparts.ConnectionEditP art.refresh(ConnectionEditPart.java:1119)
>
> at
> org.eclipse.gef.editparts.AbstractConnectionEditPart.setTarg et(AbstractConnectionEditPart.java:295)
>
> at
> org.eclipse.gef.editparts.AbstractGraphicalEditPart.addTarge tConnection(AbstractGraphicalEditPart.java:278)
>
> at
> org.eclipse.gef.editparts.AbstractGraphicalEditPart.refreshT argetConnections(AbstractGraphicalEditPart.java:674)
>
> at
> org.eclipse.stp.bpmn.diagram.edit.parts.ActivityEditPart.ref reshTargetConnections(ActivityEditPart.java:645)
>
> ... 56 more
>
> !ENTRY org.eclipse.ui 4 0 2009-03-01 12:59:43.171
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable
> (java.lang.NullPointerException)
> at org.eclipse.swt.SWT.error(SWT.java:3777)
> at org.eclipse.swt.SWT.error(SWT.java:3695)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:136)
>
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3800)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3425)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
>
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
> at
> org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
>
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>
> 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: 549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> Caused by: java.lang.NullPointerException
> at
> org.eclipse.draw2d.RelativeBendpoint.getLocation(RelativeBen dpoint.java:63)
> at
> org.eclipse.gmf.runtime.diagram.ui.editparts.ShapeCompartmen tEditPart$ConnectionRefreshMgr.refreshConnections(ShapeCompa rtmentEditPart.java:165)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.editparts.ShapeCompartmen tEditPart.forceRefreshConnections(ShapeCompartmentEditPart.j ava:612)
>
> at
> org.eclipse.gmf.runtime.diagram.ui.editparts.ShapeCompartmen tEditPart$2.run(ShapeCompartmentEditPart.java:595)
>
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:133)
>
> ... 22 more
>
> Best Regards,
>
> Romulo Arpini
>
|
|
| | |
Re: Problems when connecting two elements [message #9542 is a reply to message #9518] |
Sun, 01 March 2009 23:59 |
Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
You should make sure the version you downloaded is active. I suppose the
problem might come from a corrupted diagram, try creating a new one, see
if you reproduce the problem.
Thanks,
Antoine
Rômulo Arpini wrote:
> Well, I tried with that update and got the exactly same error with the
> exactly same log.
> Am I doing something really wrong?
>
> Best Regards,
>
> Romulo Ar
>
|
|
|
Re: Problems when connecting two elements [message #9565 is a reply to message #9542] |
Mon, 02 March 2009 00:42 |
Rômulo rpini Messages: 36 Registered: July 2009 |
Member |
|
|
Hi Antoine,
Thanks again for you reply.
And yeah, I downloaded the latest versions of eclipse. And if I save the
diagram with the flow connector like that, when I open again, I get a
message saying the diagram is corrupted.
And I m trying to install for about 5 days, and I tried many times to
create a new diagram, so I dont think thatŽs it. :(
Just a while ago I downloaded ganymed from eclipse website on my other
computer and updated with bpmn project feature once again. Got the exactly
same problem. :(
Do you know any website that has a build of eclipse with bpmn? Just to see
if itŽs my computer or something like that. Because I want to be able to
install BPMN and even change the source code, because I will need on my
final project in my graduation.
Best Regards,
Romulo Arpini
Antoine Toulme wrote:
> You should make sure the version you downloaded is active. I suppose the
> problem might come from a corrupted diagram, try creating a new one, see
> if you reproduce the problem.
> Thanks,
> Antoine
> Rômulo Arpini wrote:
>> Well, I tried with that update and got the exactly same error with the
>> exactly same log.
>> Am I doing something really wrong?
>>
>> Best Regards,
>>
>> Romulo Ar
>>
|
|
|
Re: Problems when connecting two elements [message #9589 is a reply to message #9565] |
Mon, 02 March 2009 10:00 |
Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
Romulo Arpini wrote:
> Hi Antoine,
>
> Thanks again for you reply.
>
> And yeah, I downloaded the latest versions of eclipse.
You mean you downloaded 3.5M5 ? Or a nightly build ?
And if I save the
> diagram with the flow connector like that, when I open again, I get a
> message saying the diagram is corrupted.
>
> And I m trying to install for about 5 days, and I tried many times to
> create a new diagram, so I dont think thatŽs it. :(
>
> Just a while ago I downloaded ganymed from eclipse website on my other
> computer and updated with bpmn project feature once again. Got the
> exactly same problem. :(
OK, file a bug please.
>
> Do you know any website that has a build of eclipse with bpmn? Just to
> see if itŽs my computer or something like that. Because I want to be
> able to install BPMN and even change the source code, because I will
> need on my final project in my graduation.
>
You can try the Amalgam downloads. But if you are to modify the souce
code, why don't you start with it ? Just get the classic SDK, the latest
GMF, EMF, EMF validation, EMF query, EMF transaction, GEF, get the
sources and run.
> Best Regards,
>
> Romulo Arpini
>
> Antoine Toulme wrote:
>
>> You should make sure the version you downloaded is active. I suppose
>> the problem might come from a corrupted diagram, try creating a new
>> one, see if you reproduce the problem.
>
>> Thanks,
>
>> Antoine
>
>> Rômulo Arpini wrote:
>>> Well, I tried with that update and got the exactly same error with the
>>> exactly same log.
>>> Am I doing something really wrong?
>>>
>>> Best Regards,
>>>
>>> Romulo Ar
>>>
>
>
|
|
|
Re: Problems when connecting two elements [message #9610 is a reply to message #9589] |
Mon, 02 March 2009 22:13 |
Rômulo rpini Messages: 36 Registered: July 2009 |
Member |
|
|
Antoine Toulme wrote:
> You mean you downloaded 3.5M5 ? Or a nightly build ?
From here: http://www.eclipse.org/downloads/ and here
http://www.intalio.com/products/eclipse-ganymede-download/
> You can try the Amalgam downloads. But if you are to modify the souce
> code, why don't you start with it ? Just get the classic SDK, the latest
> GMF, EMF, EMF validation, EMF query, EMF transaction, GEF, get the
> sources and run.
'Cause like I said I am really a beginner, and I really just want to make
it first.
And, hey, I downloaded Amalgam from here
http://download.eclipse.org/modeling/amalgam/modeler/downloa ds/drops/S20090214-0743/index.php
and I thought it will work beucase it already has bpmn modeler but guess
what? The same problem again. I just dont know what to do anymore. : (
Thanks anyway.
Best Regards,
Romulo Arpini
|
|
|
Re: Problems when connecting two elements [message #9634 is a reply to message #9610] |
Mon, 02 March 2009 23:44 |
Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
Romulo Arpini wrote:
> Antoine Toulme wrote:
>
>> You mean you downloaded 3.5M5 ? Or a nightly build ?
>
> From here: http://www.eclipse.org/downloads/ and here
> http://www.intalio.com/products/eclipse-ganymede-download/
So you downloaded an old build.
Please try with the latest 3.5.
>
>> You can try the Amalgam downloads. But if you are to modify the souce
>> code, why don't you start with it ? Just get the classic SDK, the
>> latest GMF, EMF, EMF validation, EMF query, EMF transaction, GEF, get
>> the sources and run.
>
> 'Cause like I said I am really a beginner, and I really just want to
> make it first.
>
> And, hey, I downloaded Amalgam from here
> http://download.eclipse.org/modeling/amalgam/modeler/downloa ds/drops/S20090214-0743/index.php
> and I thought it will work beucase it already has bpmn modeler but guess
> what? The same problem again. I just dont know what to do anymore. : (
You should get the libs I gave you the list of above, get the source or
the latest binaries, and get going.
Thanks,
Antoine
>
> Thanks anyway.
>
> Best Regards,
>
> Romulo Arpini
>
|
|
|
Re: Problems when connecting two elements [message #9657 is a reply to message #9634] |
Tue, 03 March 2009 02:36 |
Rômulo rpini Messages: 36 Registered: July 2009 |
Member |
|
|
Thanks for your advice.
I m trying with 3.50M5 but everytime I select bpmn project feature and try
to install, I get:
Cannot complete the install because some dependencies are not satisfiable
"com.ibm.icu [3.6.0,4.0.0)" and "com.ibm.icu [4.0.0.v20081201]" are both
required, but are not compatible with each other.
"com.ibm.icu [3.6.0,4.0.0)" and "com.ibm.icu [4.0.0.v20081201]" are both
required, but are not compatible with each other.
"org.eclipse.sdk.feature.group
3.5.0.v20090202-7Q7bA7DPQ-nJD6V1BcTa0VNKvoomuLjMETt2u4z0hI8t v " requires
"org.eclipse.platform.feature.group
[3.5.0.v20090202-9iD4G4MFupibor-KWmSqD2A37suAs71R]"
"org.eclipse.sdk.ide 3.5.0.I20090202-1535" requires
"org.eclipse.sdk.feature.group
[3.5.0.v20090202-7Q7bA7DPQ-nJD6V1BcTa0VNKvoomuLjMETt2u4z0hI8 tv] "
"org.eclipse.cvs.feature.group 1.1.100.v20090123-7E79FBV9BJ99pAKG_13J33"
requires "org.eclipse.platform.feature.group [3.3.0,4.0.0)"
"org.eclipse.sdk.feature.group
3.5.0.v20090202-7Q7bA7DPQ-nJD6V1BcTa0VNKvoomuLjMETt2u4z0hI8t v " requires
"org.eclipse.pde.feature.group [3.5.0.v20090123-7Z7YF8NFE-z0VXeYpohDfFNL]"
"org.eclipse.jdt.feature.group 3.5.0.v20090202-7p84FGDFHmHulDaDz-tFp1nr"
requires "org.eclipse.platform.feature.group [3.4.0,4.0.0)"
"org.eclipse.pde.feature.group 3.5.0.v20090123-7Z7YF8NFE-z0VXeYpohDfFNL"
requires "org.eclipse.jdt.feature.group [3.0.0,4.0.0)"
"org.eclipse.pde.feature.group 3.5.0.v20090123-7Z7YF8NFE-z0VXeYpohDfFNL"
requires "org.eclipse.platform.feature.group [3.0.0,4.0.0)"
"org.eclipse.sdk.feature.group
3.5.0.v20090202-7Q7bA7DPQ-nJD6V1BcTa0VNKvoomuLjMETt2u4z0hI8t v " requires
"org.eclipse.cvs.feature.group [1.1.100.v20090123-7E79FBV9BJ99pAKG_13J33]"
"org.eclipse.rcp.feature.group 3.5.0.v20090202-9RA1FwwFr-TNqU7GSg_iVTQ"
requires "com.ibm.icu [4.0.0.v20081201]"
"org.eclipse.platform.feature.group
3.5.0.v20090202-9iD4G4MFupibor-KWmSqD2A37suAs71R" requires
"org.eclipse.rcp.feature.group [3.5.0.v20090202-9RA1FwwFr-TNqU7GSg_iVTQ]"
"org.eclipse.sdk.feature.group
3.5.0.v20090202-7Q7bA7DPQ-nJD6V1BcTa0VNKvoomuLjMETt2u4z0hI8t v " requires
"org.eclipse.jdt.feature.group [3.5.0.v20090202-7p84FGDFHmHulDaDz-tFp1nr]"
Any tips? : (
Best Regards,
Romulo Arpini
|
|
|
Re: Problems when connecting two elements [message #9679 is a reply to message #9657] |
Tue, 03 March 2009 08:40 |
Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
Romulo Arpini wrote:
> Thanks for your advice.
>
> I m trying with 3.50M5 but everytime I select bpmn project feature and
> try to install,
You mean you use p2 to install this stuff.
I get:
>
> Cannot complete the install because some dependencies are not satisfiable
> "com.ibm.icu [3.6.0,4.0.0)" and "com.ibm.icu [4.0.0.v20081201]" are both
> required, but are not compatible with each other.
> "com.ibm.icu [3.6.0,4.0.0)" and "com.ibm.icu [4.0.0.v20081201]" are both
> required, but are not compatible with each other.
> "org.eclipse.sdk.feature.group
> 3.5.0.v20090202-7Q7bA7DPQ-nJD6V1BcTa0VNKvoomuLjMETt2u4z0hI8t v " requires
> "org.eclipse.platform.feature.group
> [3.5.0.v20090202-9iD4G4MFupibor-KWmSqD2A37suAs71R]" "org.eclipse.sdk.ide
> 3.5.0.I20090202-1535" requires "org.eclipse.sdk.feature.group
> [3.5.0.v20090202-7Q7bA7DPQ-nJD6V1BcTa0VNKvoomuLjMETt2u4z0hI8 tv] "
> "org.eclipse.cvs.feature.group 1.1.100.v20090123-7E79FBV9BJ99pAKG_13J33"
> requires "org.eclipse.platform.feature.group [3.3.0,4.0.0)"
> "org.eclipse.sdk.feature.group
> 3.5.0.v20090202-7Q7bA7DPQ-nJD6V1BcTa0VNKvoomuLjMETt2u4z0hI8t v " requires
> "org.eclipse.pde.feature.group
> [3.5.0.v20090123-7Z7YF8NFE-z0VXeYpohDfFNL]"
> "org.eclipse.jdt.feature.group 3.5.0.v20090202-7p84FGDFHmHulDaDz-tFp1nr"
> requires "org.eclipse.platform.feature.group [3.4.0,4.0.0)"
> "org.eclipse.pde.feature.group 3.5.0.v20090123-7Z7YF8NFE-z0VXeYpohDfFNL"
> requires "org.eclipse.jdt.feature.group [3.0.0,4.0.0)"
> "org.eclipse.pde.feature.group 3.5.0.v20090123-7Z7YF8NFE-z0VXeYpohDfFNL"
> requires "org.eclipse.platform.feature.group [3.0.0,4.0.0)"
> "org.eclipse.sdk.feature.group
> 3.5.0.v20090202-7Q7bA7DPQ-nJD6V1BcTa0VNKvoomuLjMETt2u4z0hI8t v " requires
> "org.eclipse.cvs.feature.group
> [1.1.100.v20090123-7E79FBV9BJ99pAKG_13J33]"
> "org.eclipse.rcp.feature.group 3.5.0.v20090202-9RA1FwwFr-TNqU7GSg_iVTQ"
> requires "com.ibm.icu [4.0.0.v20081201]"
> "org.eclipse.platform.feature.group
> 3.5.0.v20090202-9iD4G4MFupibor-KWmSqD2A37suAs71R" requires
> "org.eclipse.rcp.feature.group
> [3.5.0.v20090202-9RA1FwwFr-TNqU7GSg_iVTQ]"
> "org.eclipse.sdk.feature.group
> 3.5.0.v20090202-7Q7bA7DPQ-nJD6V1BcTa0VNKvoomuLjMETt2u4z0hI8t v " requires
> "org.eclipse.jdt.feature.group [3.5.0.v20090202-7p84FGDFHmHulDaDz-tFp1nr]"
> Any tips? : (
With 3.5M5, Eclipse moved from com.ibm.icu 3.4 to com.ibm.icu 4.0. Make
sure you install stuff that is at least 3.5M5, including the platform.
>
> Best Regards,
>
> Romulo Arpini
>
|
|
| |
Re: Problems when connecting two elements [message #10284 is a reply to message #9700] |
Sat, 14 March 2009 05:23 |
Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
Looks more like a sensible combination of features that make the whole
thing fail.
I'll try to assemble an all-in-one bundle for 3.4.2.
Romulo Arpini wrote:
> It didnt work. : (
>
> Could it be my pc config? And I even tried on another pc...
>
> Best Regards,
>
> Romulo Arpini
>
|
|
| |
Re: Problems when connecting two elements [message #10349 is a reply to message #10317] |
Tue, 17 March 2009 11:30 |
Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
That last build should work 3.5M5.
We are scheduled to do a new build with 3.5M6 this week.
You should use the official 1.0.1 release to run with 3.4.2.
Thanks,
Antoine
Galen Dunkleberger wrote:
> Any news on a build of the modeler that works with eclipse 3.4.2? I'm
> getting the same npe as described earlier in this thread even if i use
> the latest build
> ( http://download.eclipse.org/stp/updates/committers/2.0.0/200 903161143/site.xml).
> I can create new diagrams fine and add activities and tasks no problem
> but as soon as i try to use the flow connector it blows up.
>
|
|
| | | | |
Re: Problems when connecting two elements [message #10572 is a reply to message #10539] |
Mon, 13 April 2009 14:51 |
Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
Ralph Soika wrote:
> Hi,
>
> are there any news about this topic? I have same problems. Installed
> different builds on different eclipse installations - lot of times. ...
> I have never seen the BPMN plugin working :-(
>
> ralph
>
>
As discussed on the bug, the BPMN modeler encounters an issue with
Eclipse 3.4.2. I can only assume one of its dependencies changed and
broke something. Please comment on the bug rather than posting here.
Thanks,
Antoine
|
|
| |
Re: Problems when connecting two elements [message #10767 is a reply to message #10670] |
Wed, 15 April 2009 15:01 |
Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
Andre Souza wrote:
> hello Antoine,
>
> may you tell us which eclipse/GMF/EMF/GEF versions that the BPMN Modeler
> works?
Sure: all the 3.4.1 binaries work. So the associated EMF/GMF/GEF
versions work well.
|
|
|
Goto Forum:
Current Time: Wed Sep 25 13:48:26 GMT 2024
Powered by FUDForum. Page generated in 0.07379 seconds
|