September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (GPD-387) Config Info of Decision Handler is lost after re-opening GPD editor

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-387?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-387. --------------------------- Resolution: Out of Date > Config Info of Decision Handler is lost after re-opening GPD editor > ------------------------------------------------------------------- > > Key: GPD-387 > URL: https://issues.jboss.org/browse/GPD-387 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.7 > Reporter: Toshiya Kobayashi > Assignee: Koen Aers > Attachments: 01_configure_properties.png, 02_after_reopen.png > > > 1. Create and select a decision node in GPD editor > 2. Set Decision Handler in Properties View > 3. Set Config Info of the handler ( 01_configure_properties.png ) > 4. Close and open the GPD editor > 5. Select the decision node and see the handler's Config Info is lost in Properties View ( 02_after_reopen.png ) > Actually the config info exists in xml. If you set Config Info in Properties View again, there will be duplicate entries in xml. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-302) Generate Form Dialog is NOT auto-populated with controller variables or named transitions

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-302?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-302. --------------------------- Resolution: Out of Date > Generate Form Dialog is NOT auto-populated with controller variables or named transitions > ----------------------------------------------------------------------------------------- > > Key: GPD-302 > URL: https://issues.jboss.org/browse/GPD-302 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.6 > Environment: Eclipse 3.1.4 w/ jBPM 3.3.1.GA w/ GPD 3.1.6 > Reporter: Nobody Cares > Assignee: Koen Aers > Priority: Minor > Fix For: jBPM jPDL Designer 3.x > > > The launched dialog of a task's "Generate Form..." button is NOT automatically populated with the task's defined controller variables nor with buttons that correspond to the task's named transitions. This issue significantly hinders the usefulness of the GPD. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-386) script tag lost

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-386?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-386. --------------------------- Resolution: Out of Date > script tag lost > --------------- > > Key: GPD-386 > URL: https://issues.jboss.org/browse/GPD-386 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 4.1, jBPM jPDL Designer 4.3 > Reporter: Evgenij Dolganov > Assignee: Koen Aers > > When manually adding 'script' tag to 'transition' or task's 'on' in the XML, this tag is lost after having saved, gone back to the diagram and back to the xml. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-390) CLONE -GPD Diagram node and text positioning not saving.

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-390?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-390. --------------------------- Resolution: Out of Date > CLONE -GPD Diagram node and text positioning not saving. > -------------------------------------------------------- > > Key: GPD-390 > URL: https://issues.jboss.org/browse/GPD-390 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.7 > Environment: Eclipse 3.4, jbpm-jpdl-designer-3.1.4 > Reporter: Markus Kopka > Assignee: Koen Aers > > Using jbpm-jpdl-designer-3.1.4 gives me the following problem: > Sometimes when re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Sometimes I open my process definition in the GPD to work with it, I have to re-aligning everything. > This does not affect any configuration of nodes or the classes. But it becomes impossible to understand > the process flow from the diagram -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-358) Create jBPM Project Configuration Wizard

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-358?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-358. --------------------------- Resolution: Out of Date > Create jBPM Project Configuration Wizard > ---------------------------------------- > > Key: GPD-358 > URL: https://issues.jboss.org/browse/GPD-358 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > This wizard can be launched from the project popup menu in the Java/J2EE/Resources perspective. > A project configuration will offered and includes > - a selection of the configured jBPM runtimes > - a checkbox to import all the jBPM Libraries > Also, this includes that the 'create jBPM project' wizard in GPD 3.x will be eliminated -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-382) Add support for globalProcessScope and process-scope parameters in EsbActionHandler and EsbNotifier

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-382?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-382. --------------------------- Resolution: Out of Date > Add support for globalProcessScope and process-scope parameters in EsbActionHandler and EsbNotifier > --------------------------------------------------------------------------------------------------- > > Key: GPD-382 > URL: https://issues.jboss.org/browse/GPD-382 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.7 > Reporter: Jiri Pechanec > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.x > > > See http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_SOA... > It should be probably implemented as three-state widget (listbox) called that will contain empty value (default), process and local -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[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)

9 years, 8 months

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)

9 years, 8 months

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)

9 years, 8 months

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)

9 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2016