September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (GPD-385) Deployment of processes including Java classes fails if the workspace path contains spaces

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-385?page=com.atlassian.jira.plugin.sy... ] 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)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-363) Name of Decision box are not visible on the grahi.

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-363?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-363. --------------------------- Resolution: Out of Date > Name of Decision box are not visible on the grahi. > -------------------------------------------------- > > Key: GPD-363 > URL: https://issues.jboss.org/browse/GPD-363 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM jPDL Designer 4.0.0.GA > Reporter: Alexandre Navarro > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > Name of Decision box are not visible on the grahi. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-292) Enhance Node Pluggability

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-292?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-292. --------------------------- Resolution: Out of Date > Enhance Node Pluggability > ------------------------- > > Key: GPD-292 > URL: https://issues.jboss.org/browse/GPD-292 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > It should be possible to add nodes by adding a jar file (containing a configuration and possibly some java classes and icons) in a well-defined location. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-140) when working with large process definitions, screen jumps to top whenever new nodes added in designer

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-140?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-140. --------------------------- Resolution: Out of Date > when working with large process definitions, screen jumps to top whenever new nodes added in designer > ----------------------------------------------------------------------------------------------------- > > Key: GPD-140 > URL: https://issues.jboss.org/browse/GPD-140 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM JPDL Designer 3.1.0.beta2 > Environment: osx macbook pro, eclipse 3.3.0, designer plugin 3.1.0 beta 1, beta 2, CR1 > Reporter: Ross McDonald > Assignee: Koen Aers > Priority: Trivial > Fix For: jBPM jPDL Designer 3.x, jBPM jPDL Designer 4.x > > > Hi, > when working with large process diagrams, if I am scrolled down to the bottom of the view, and add a new node, when the screen is updated it jumps back up to the top, so I need to scroll down again. > Obviously when adding many nodes, this costs time, its just a trivial thing. > Cheers > Ross -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-244) Graphical editor does not allow configuring signal type

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-244?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-244. --------------------------- Resolution: Out of Date > Graphical editor does not allow configuring signal type > ------------------------------------------------------- > > Key: GPD-244 > URL: https://issues.jboss.org/browse/GPD-244 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.3, jBPM jPDL Designer 3.1.3.SP2, jBPM jPDL Designer 3.1.4, jBPM jPDL Designer 3.1.5 > Reporter: George Gastaldi > Assignee: Koen Aers > Priority: Trivial > Fix For: jBPM jPDL Designer 3.x > > > Each task-node may have a "signal" attribute associated, that is: > -unsynchronized > -first > -first-wait > -last > -last-wait > -never > . This is not shown on the Graphical Designer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-336) image generation fails

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-336?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-336. --------------------------- Resolution: Out of Date > image generation fails > ---------------------- > > Key: GPD-336 > URL: https://issues.jboss.org/browse/GPD-336 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Tom Baeyens > Assignee: Koen Aers > Priority: Optional > Fix For: jBPM jPDL Designer 4.x > > > image generation seems to work for org.jbpm.examples.async.activity > but it seems to fail for org.jbpm.examples.async.fork. in that case I get an image with only a diagonal line. > koen, do you get the same with that example ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-377) Saving Java file wrecks deployment settings

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-377?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-377. --------------------------- Resolution: Out of Date > Saving Java file wrecks deployment settings > ------------------------------------------- > > Key: GPD-377 > URL: https://issues.jboss.org/browse/GPD-377 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.7 > Environment: GDP 3.1.7 > Eclipse Galileo Java EE 20090621-0832 > Linux Ubuntu 2009.04 > Reporter: Nicolas Raoul > Assignee: Koen Aers > Priority: Minor > Fix For: jBPM jPDL Designer 3.x > > > It works fine, but there is something silly: > Everytime I save a Java file, the deployment's "Java Classes and Resources" settings are automatically reconfigured to something that does not work. > It seems that all Java classes that are not directly called from the process definition file get deselected. Like if I would wrote all of the code in just one class... > (and of course if options could be saved to survive Eclipse restarts, that would be even better) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-206) Show simlane assignment in task node

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-206?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-206. --------------------------- Resolution: Out of Date > Show simlane assignment in task node > ------------------------------------ > > Key: GPD-206 > URL: https://issues.jboss.org/browse/GPD-206 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Reporter: Ruben Marrero > Assignee: Koen Aers > Priority: Trivial > Fix For: jBPM jPDL Designer 3.x, jBPM jPDL Designer 4.x > > > It would be very useful if the task would show which swimlane is assigned to. > Thanks -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-154) process image rendered incorrectly for large process definition

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-154?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-154. --------------------------- Resolution: Out of Date > process image rendered incorrectly for large process definition > --------------------------------------------------------------- > > Key: GPD-154 > URL: https://issues.jboss.org/browse/GPD-154 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Environment: mac osx, tomcat 5.0.28 > Reporter: Ross McDonald > Assignee: Koen Aers > Priority: Minor > Fix For: jBPM jPDL Designer 3.x > > > Hi, > then I create a large process, and extend to the left beyond the original boundary, by placing and element in the designer and dragging, so scrollbars appear, the image when rendered in the console is offset incorrectly while on any given node, > cheers > Ross -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-14) Lay out Algorithm

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-14?page=com.atlassian.jira.plugin.sys... ] Koen Aers resolved GPD-14. -------------------------- Resolution: Out of Date > Lay out Algorithm > ----------------- > > Key: GPD-14 > URL: https://issues.jboss.org/browse/GPD-14 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Minor > Fix For: jBPM jPDL Designer 3.x > > > Integrate a layout algorithm that is used when users add nodes to the xml directly to lay out the newly created components in an orderly fashion on the graphical canvas. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2016