[JBoss jBPM] - gpd from cvs head - process flow editor broken
by andyredhead
Hi,
I'm not sure if this is the appropriate forum (perhaps it should go into the developers forum as its not a problem with a formal release)...
I've just done a cvs update against the head and built the gpd.
I've tried to start editing a process definition but the editor won't start up.
In the eclipse .metadata log file there is a message about "IFormColors cannot be resolved" (full copy of the logfile below).
Any idea what I need to do to get this working?
Cheers,
Andy
| eclipse.buildId=M20070112-1200
| java.version=1.5.0_07
| java.vendor=Sun Microsystems Inc.
| BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
| Command-line arguments: -os win32 -ws win32 -arch x86
|
| !ENTRY org.eclipse.ui 4 4 2007-07-25 15:15:31.656
| !MESSAGE Unhandled event loop exception
|
| !ENTRY org.eclipse.ui 4 0 2007-07-25 15:15:31.656
| !MESSAGE Unresolved compilation problems:
| The import org.eclipse.ui.forms.IFormColors cannot be resolved
| IFormColors cannot be resolved
| IFormColors cannot be resolved
| IFormColors cannot be resolved
| IFormColors cannot be resolved
|
| !STACK 0
| java.lang.Error: Unresolved compilation problems:
| The import org.eclipse.ui.forms.IFormColors cannot be resolved
| IFormColors cannot be resolved
| IFormColors cannot be resolved
| IFormColors cannot be resolved
| IFormColors cannot be resolved
|
| at org.jbpm.gd.jpdl.deployment.DeploymentForm.<init>(Unknown Source)
| at org.jbpm.gd.jpdl.editor.JpdlDeploymentEditorPage.createForm(Unknown Source)
| at org.jbpm.gd.jpdl.editor.JpdlDeploymentEditorPage.createPartControl(Unknown Source)
| at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:183)
| at org.jbpm.gd.common.editor.Editor.addPage(Unknown Source)
| at org.jbpm.gd.jpdl.editor.JpdlEditor.createPages(Unknown Source)
| at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:276)
| at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)
| at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
| at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
| at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:214)
| at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2595)
| at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2528)
| at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2520)
| at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2505)
| at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
| at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2500)
| at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:288)
| at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:280)
| at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:184)
| at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
| at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
| at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
| at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
| at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
| at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
| at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
| at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
| at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
| at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
| at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
| at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
| at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
| 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.invokeFramework(Main.java:336)
| at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
| at org.eclipse.core.launcher.Main.run(Main.java:977)
| at org.eclipse.core.launcher.Main.main(Main.java:952)
|
| !ENTRY org.eclipse.ui 4 4 2007-07-25 15:15:36.109
| !MESSAGE Unhandled event loop exception
|
| !ENTRY org.eclipse.ui 4 0 2007-07-25 15:15:36.109
| !MESSAGE Unresolved compilation problems:
| The import org.eclipse.ui.forms.IFormColors cannot be resolved
| IFormColors cannot be resolved
| IFormColors cannot be resolved
| IFormColors cannot be resolved
| IFormColors cannot be resolved
|
| !STACK 0
| java.lang.Error: Unresolved compilation problems:
| The import org.eclipse.ui.forms.IFormColors cannot be resolved
| IFormColors cannot be resolved
| IFormColors cannot be resolved
| IFormColors cannot be resolved
| IFormColors cannot be resolved
|
| at org.jbpm.gd.jpdl.deployment.DeploymentForm.<init>(Unknown Source)
| at org.jbpm.gd.jpdl.editor.JpdlDeploymentEditorPage.createForm(Unknown Source)
| at org.jbpm.gd.jpdl.editor.JpdlDeploymentEditorPage.createPartControl(Unknown Source)
| at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:183)
| at org.jbpm.gd.common.editor.Editor.addPage(Unknown Source)
| at org.jbpm.gd.jpdl.editor.JpdlEditor.createPages(Unknown Source)
| at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:276)
| at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)
| at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
| at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
| at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290)
| at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:140)
| at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
| at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
| at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:394)
| at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1144)
| at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1097)
| at org.eclipse.ui.internal.PartStack.presentationSelectionChanged(PartStack.java:795)
| at org.eclipse.ui.internal.PartStack.access$1(PartStack.java:781)
| at org.eclipse.ui.internal.PartStack$1.selectPart(PartStack.java:123)
| at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation$1.handleEvent(TabbedStackPresentation.java:126)
| at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:267)
| at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:276)
| at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder.access$1(DefaultTabFolder.java:1)
| at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder$2.handleEvent(DefaultTabFolder.java:84)
| at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
| at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:709)
| at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3171)
| at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1953)
| at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:288)
| at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
| at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
| at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
| at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
| at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
| at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
| at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
| at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
| at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
| at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
| at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
| at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
| at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
| 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.invokeFramework(Main.java:336)
| at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
| at org.eclipse.core.launcher.Main.run(Main.java:977)
| at org.eclipse.core.launcher.Main.main(Main.java:952)
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067414#4067414
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067414
18Â years, 9Â months
[JBoss Seam] - Re: How bad is unused conversations?
by stephen.friedrich
Hm, I think explicit conversation ids only make sense when the application logic naturally suggests them. (Like using an article id for an article editor - it really makes no sense to edit the very same article in different conversations).
To make matters more concrete: Image a UI that shows a tabbed pane where each tab hosts a possible step of interactions.
So you want each tab to have a conversation of its own. However if you simply assign fixed conversation ids you will loose the ability to open new browser windows/tabs.
There's a lot of documentation how context demarcation technically works, but there is close to none how it it relates to interaction design.
Note that you would not have to think twice about how to implement this in a rich client: Each tab instance would simply holds its model which is "commited" at the final step of the task.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067412#4067412
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067412
18Â years, 9Â months