[JBoss JIRA] Created: (GPD-141) IType.getCompilationUnit() can be null if handler class is in jar, leads to event loop exception
by Matthias Hanisch (JIRA)
IType.getCompilationUnit() can be null if handler class is in jar, leads to event loop exception
------------------------------------------------------------------------------------------------
Key: GPD-141
URL: http://jira.jboss.com/jira/browse/GPD-141
Project: JBoss jBPM GPD
Issue Type: Bug
Components: jpdl
Affects Versions: jBPM JPDL Designer 3.1.0.CR
Environment: Eclipse 3.2 on Windows 2000
Reporter: Matthias Hanisch
Assigned To: Koen Aers
Following part of my processdefinition.xml:
<event type="node-leave">
<action class="x.y.z.MyClass" name="An Action">
<arg>
anArg
</arg>
</action>
</event>
MyClass is in a jar which is added to the classpath of the Process Project. Saving throws an event loop exception in Error Log View with the following stack.
Caused by: org.eclipse.jface.util.Assert$AssertionFailedException: null argument;
at org.eclipse.jface.util.Assert.isNotNull(Assert.java:150)
at org.eclipse.jface.util.Assert.isNotNull(Assert.java:126)
at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:577)
at org.eclipse.jface.viewers.CheckboxTreeViewer.setCheckedElements(CheckboxTreeViewer.java:431)
at org.jbpm.gd.jpdl.deployment.IncludeInDeploymentTreeViewer.setCheckedElements(IncludeInDeploymentTreeViewer.java:61)
at org.jbpm.gd.jpdl.deployment.DeploymentForm$17.run(DeploymentForm.java:635)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
The problem is, that DeploymentForm.getElementsToCheckFor() does not respect that MyClass returns null for getCompilationUnit(). As a consequence, setCheckedElements is called with null in the Object[].
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (GPD-136) Widget is disposed in Task Controller Variables Table
by Matthias Hanisch (JIRA)
Widget is disposed in Task Controller Variables Table
-----------------------------------------------------
Key: GPD-136
URL: http://jira.jboss.com/jira/browse/GPD-136
Project: JBoss jBPM GPD
Issue Type: Bug
Components: jpdl
Affects Versions: jBPM JPDL Designer 3.1.0.beta2
Environment: Eclipse 3.2.2 on Windows 2000
Reporter: Matthias Hanisch
Assigned To: Koen Aers
Select a Task Node. Go to Properties View.
Select Tasks:<task>:Controller (default).
Add two variables, remove the second.
Error Log view contains the following SWT Exception:
org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:3374)
at org.eclipse.swt.SWT.error(SWT.java:3297)
at org.eclipse.swt.SWT.error(SWT.java:3268)
at org.eclipse.swt.widgets.Widget.error(Widget.java:435)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:330)
at org.eclipse.swt.widgets.Control.setVisible(Control.java:2642)
at org.jbpm.gd.jpdl.util.VariableTableItemWrapper.applyName(VariableTableItemWrapper.java:164)
at org.jbpm.gd.jpdl.util.VariableTableItemWrapper.cancelEditing(VariableTableItemWrapper.java:150)
at org.jbpm.gd.jpdl.util.VariableTableCellClickedResolver.mouseDown(VariableTableCellClickedResolver.java:25)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:133)
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(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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)
After that, table input is not working anymore ("Mapped Name" column not editable anymore, for example).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (GPD-9) save deployment options
by Brice Ruth (JIRA)
save deployment options
-----------------------
Key: GPD-9
URL: http://jira.jboss.com/jira/browse/GPD-9
Project: JBoss jBPM GPD
Issue Type: Feature Request
Affects Versions: 3.0.11
Reporter: Brice Ruth
Assigned To: Koen Aers
The current jBPM Process Designer plugin for Eclipse does not save deployment settings for a process definition. It would be useful to set remote deploy settings as a workspace preference (host/port/path). Then, what files are to be deployed (gpd.xml, processdefinition.xml, processimage.xml, src files, etc.) should be saved per process, and stored as part of the project/process files (whichever, just not in .metadata, so it can be committed to CVS and shared by a team).
JBoss Support Case: 00012512
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month