Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324251 - When extending an entity from a class diagram the "Select domain model element" dialog does not offer artifacts in Installable Modules.
Summary: When extending an entity from a class diagram the "Select domain model elemen...
Status: CLOSED INVALID
Alias: None
Product: Tigerstripe
Classification: Technology
Component: Diagrams (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 0.5M0   Edit
Assignee: Navid Mehregani CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-01 17:30 EDT by Jim Strawn CLA
Modified: 2010-09-13 16:59 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Strawn CLA 2010-09-01 17:30:48 EDT

    
Comment 1 Jim Strawn CLA 2010-09-01 17:48:52 EDT
When creating relationships (to or from) an Entity in a Class Diagram the "Select domain model element" diagram does not show any artifacts that exist in installable modules.

1. Create a new class diagram (or existing, doesn't matter)
2. Create a new entity (using the palette)
3. Click on the new entity to enable the "relationship creation arrows", for lack of a better term :-)
4. Click on the arrow pointing away from the entity ("relationship to"). This brings up the options 
     selected as defined in 5.
5. Create Extends to -> Existing Element

The resulting dialog (Select domain model element) should contain artifacts that reside in Installable Modules, along with those artifacts in workspace projects.

This is also reproducible with other relationships. 

P2:

If a user wants to implement an interface and there is not an interface in the local workspace an exception is thrown as there are no elements to display in the dialog (dialog disappears).

Log message

!ENTRY org.eclipse.ui 4 0 2010-09-01 16:47:47.561
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
	at org.eclipse.draw2d.ToolTipHelper$3.mouseEnter(ToolTipHelper.java:133)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:187)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3543)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1250)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1273)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
	at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1079)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3441)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3100)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
	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(EclipseStarter.java:368)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Comment 2 Richard Craddock CLA 2010-09-13 08:32:30 EDT
I beleive this is a mis-interpretation of the functioning of this dialog.

(I was similarly confused until I looked at the code).

The dialog that pops up when you drop teh end on "nothing" and select the "existing elemnt" option is a List of elements THAT ARE ALREADY ON THE DIAGRAM, and *NOT* a complete list of elements in the model.

If there are eleemnst on the digram from an installable module, they are listed.

The only question for me question is whether the intent of this option clear enough from the label...

I am tempted to close this bug......
Comment 3 Jim Strawn CLA 2010-09-13 16:59:33 EDT
I now agree with richard. I believe that the stack trace below is  unrelated to the issue. Closing as invalid.

Note that an enhancement request has been created to capture this new feature (See https://bugs.eclipse.org/bugs/show_bug.cgi?id=325142)