Eclipse Community Forums: Visual Editor (VE)

Help

Home

Home » Archived » Visual Editor (VE) » VE & omondo

Show: Today's Messages :: Show Polls :: Message Navigator

VE & omondo [message #85170]

Tue, 29 March 2005 17:03

Elena Demeter

Messages: 152
Registered: July 2009

Senior Member

Hello,

I have installed eclipse 3.0.1, emf 2.0.1, gef 3.0.1 and omondo 1.1.0...

I have also installed the visual editor. I have imported the plugins of
the visual editor.

If I am trying to open it with "Class Diagramm Editor" I get the message
below. There are not created any diagramms. If I make a diagramm from my
classes, I do not get this error.

Does somebody know why I get this message?
What can I do to solve the problem ?

Thank you very much in advance
Elena

java.lang.IllegalArgumentException: Attempted to beginRule:
com.omondo.uml.g.a.a@9cf542, does not match outer scope rule:
com.omondo.uml.g.a.a@9cf542
at org.eclipse.core.internal.runtime.Assert.isLegal(Assert.java :58)
at
org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJ ob.java:106)
at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java :200)
at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJo bs.java:80)
at
org.eclipse.core.internal.jobs.JobManager.beginRule(JobManag er.java:170)
at
org.eclipse.core.internal.resources.WorkManager.checkIn(Work Manager.java:95)
at
org.eclipse.core.internal.resources.Workspace.prepareOperati on(Workspace.java:1628)
at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1668)
at
org.eclipse.search2.internal.ui.text.MarkerHighlighter.addHi ghlights(MarkerHighlighter.java:41)
at
org.eclipse.search2.internal.ui.text.EditorAnnotationManager .addAnnotations(EditorAnnotationManager.java:164)
at
org.eclipse.search2.internal.ui.text.EditorAnnotationManager .addAnnotations(EditorAnnotationManager.java:159)
at
org.eclipse.search2.internal.ui.text.EditorAnnotationManager .setSearchResult(EditorAnnotationManager.java:75)
at
org.eclipse.search2.internal.ui.text.WindowAnnotationManager .startHighlighting(WindowAnnotationManager.java:76)
at
org.eclipse.search2.internal.ui.text.WindowAnnotationManager .access$1(WindowAnnotationManager.java:69)
at
org.eclipse.search2.internal.ui.text.WindowAnnotationManager $1.partVisible(WindowAnnotationManager.java:59)
at
org.eclipse.ui.internal.PartListenerList2$7.run(PartListener List2.java:139)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:616)
at org.eclipse.core.runtime.Platform.run(Platform.java:747)
at
org.eclipse.ui.internal.PartListenerList2.firePartVisible(Pa rtListenerList2.java:137)
at
org.eclipse.ui.internal.WWinPartService$1.partVisible(WWinPa rtService.java:43)
at
org.eclipse.ui.internal.PartListenerList2$7.run(PartListener List2.java:139)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:616)
at org.eclipse.core.runtime.Platform.run(Platform.java:747)
at
org.eclipse.ui.internal.PartListenerList2.firePartVisible(Pa rtListenerList2.java:137)
at
org.eclipse.ui.internal.WorkbenchPage$1.propertyChange(Workb enchPage.java:139)
at org.eclipse.ui.internal.LayoutPart.setVisible(LayoutPart.jav a:268)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:31 7)
at
org.eclipse.ui.internal.presentations.PresentablePart.setVis ible(PresentablePart.java:122)
at
org.eclipse.ui.internal.presentations.DefaultPartPresentatio n.selectPart(DefaultPartPresentation.java:1116)
at
org.eclipse.ui.internal.PartStack.refreshPresentationSelecti on(PartStack.java:946)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.jav a:921)
at org.eclipse.ui.internal.EditorStack.setSelection(EditorStack .java:196)
at
org.eclipse.ui.internal.EditorStack.setVisibleEditor(EditorS tack.java:200)
at
org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(Ed itorAreaHelper.java:338)
at
org.eclipse.ui.internal.EditorAreaHelper.openEditor(EditorAr eaHelper.java:268)
at org.eclipse.ui.internal.EditorManager$4.run(EditorManager.ja va:694)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
at
org.eclipse.ui.internal.EditorManager.createEditorTab(Editor Manager.java:683)
at
org.eclipse.ui.internal.EditorManager.openInternalEditor(Edi torManager.java:779)
at
org.eclipse.ui.internal.EditorManager.openEditorFromDescript or(EditorManager.java:582)
at
org.eclipse.ui.internal.EditorManager.openEditor(EditorManag er.java:570)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched( WorkbenchPage.java:2244)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(Workben chPage.java:2177)
at org.eclipse.ui.internal.WorkbenchPage.access$6(WorkbenchPage .java:2169)
at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.ja va:2156)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2151)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:299)
at
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInE ditor(EditorUtility.java:137)
at
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInE ditor(EditorUtility.java:110)
at com.omondo.uml.a.a.ab.a(SourceFile:60)
at com.omondo.uml.f.c.b.a.a9.int(SourceFile:113)
at com.omondo.uml.UMLDiagramUI.a(SourceFile:226)
at com.omondo.uml.OpenClassDiagramAction.run(SourceFile:72)
at
org.eclipse.ui.internal.PluginAction.runWithEvent(PluginActi on.java:276)
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:915)
at
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:866)
at
org.eclipse.jface.action.ActionContributionItem$7.handleEven t(ActionContributionItem.java:785)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:2772)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2431)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1377)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:254)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:96)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:335)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:273)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:129)
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.core.launcher.Main.basicRun(Main.java:185)
at org.eclipse.core.launcher.Main.run(Main.java:704)
at org.eclipse.core.launcher.Main.main(Main.java:688)

Report message to a moderator

Re: VE & omondo [message #85216 is a reply to message #85170]

Wed, 30 March 2005 06:46

Elena Demeter

Messages: 152
Registered: July 2009

Senior Member

Hello,

a little correction: I got this error yestreday if I did "UML | Reverse
Engineering" and the beginning of the error was:

------------------------------------------------------------ ---------------
!ENTRY org.eclipse.core.runtime 4 2 Mrz 29, 2005 19:19:09.593
!MESSAGE Problems occurred when invoking code from plug-in:
"org.eclipse.core.runtime".
!STACK 0
java.lang.IllegalArgumentException: Attempted to beginRule:
com.omondo.uml.g.a.a@9cf542, does not match outer scope rule:
com.omondo.uml.g.a.a@9cf542
at org.eclipse.core.internal.runtime.Assert.isLegal(Assert.java :5
------------------------------------------------------------ -----------------

After I imported "org.eclipse.core.runtime" I did not get any error but I
also did not get diagramms created.

1. Does somebody know what are the reasons for not creation of diagramms ?

2. Are there any other tools for creating a class diagramms of VE that are
compatibel with VE ???

I have also seen "argoUML" and "Understand for Java". "Understand for
Java" creates a class diagramm only for one class.

Thanks :o)
Elena

Report message to a moderator

Re: VE & omondo [message #85246 is a reply to message #85216]

Wed, 30 March 2005 15:19

Eclipse User

Originally posted by: richkulp.us.NO_SPAM.ibm.com

VE and omondo have nothing to do with each other. VE works on the Java
code, not UML diagrams. So if you are having problems with the omondo,
you will need to go to them for support.

--
Thanks,
Rich Kulp

Report message to a moderator