[jboss-jira] [JBoss JIRA] (GPD-385) Deployment of processes including Java classes fails if the workspace path contains spaces
Koen Aers (JIRA)
issues at jboss.org
Mon Sep 5 11:22:00 EDT 2016
[ https://issues.jboss.org/browse/GPD-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koen Aers resolved GPD-385.
---------------------------
Resolution: Out of Date
> Deployment of processes including Java classes fails if the workspace path contains spaces
> ------------------------------------------------------------------------------------------
>
> Key: GPD-385
> URL: https://issues.jboss.org/browse/GPD-385
> Project: jBPM GPD
> Issue Type: Bug
> Components: jpdl
> Affects Versions: jBPM jPDL Designer 3.1.7
> Environment: - JBDS on Windows or Linux
> - workspace path contains spaces
> Reporter: Martin Weiler
> Assignee: Koen Aers
>
> 1. Use a workspace which contains spaces
> 2. Create a new jBPM project with the default process and action handler classes
> 3. Open the processdefinition and go to the Deployment tab
> 4. Make sure the ActionHandler class is included in the deployment
> 5. Hit 'Deploy Process Archive...'
> ERROR: Exception happened while deploying
> Exception Stack Trace (from Error Log):
> java.lang.NullPointerException
> at org.jbpm.gd.jpdl.util.ProcessDeployer.addClassOrResource(Unknown Source)
> at org.jbpm.gd.jpdl.util.ProcessDeployer.addClassesAndResources(Unknown Source)
> at org.jbpm.gd.jpdl.util.ProcessDeployer.createParBytes(Unknown Source)
> at org.jbpm.gd.jpdl.util.ProcessDeployer.access$1(Unknown Source)
> at org.jbpm.gd.jpdl.util.ProcessDeployer$1.run(Unknown Source)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.jbpm.gd.jpdl.util.ProcessDeployer.showProgressMonitorDialog(Unknown Source)
> at org.jbpm.gd.jpdl.util.ProcessDeployer.deploy(Unknown Source)
> at org.jbpm.gd.jpdl.deployment.DeploymentForm$1.widgetSelected(Unknown Source)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490)
> 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: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(EclipseStarter.java:386)
> 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:549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
> (Note: deploying the process without the action handler classes works!)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list