September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (GPD-308) prevent empty names

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-308?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-308. --------------------------- Resolution: Out of Date > prevent empty names > ------------------- > > Key: GPD-308 > URL: https://issues.jboss.org/browse/GPD-308 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Tom Baeyens > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > in end state example, i see you generated an empty name. that should be prevented if possible. the fact that this still parses without exception is actually a bug. > <process name="EndState" xmlns="http://jbpm.org/4/jpdl"> > <start g="16,96,48,48"> > <transition to="get return code" name=""/> > </start> > <state g="96,94,110,52" name="get return code"> > <transition g="150,63:-36,11" name="200" to="ok"/> > <transition g=":-16,-27" name="400" to="bad request"/> > <transition g="150,177:-33,-32" name="500" to="internal server error"/> > </state> > <end g="239,40,48,48" name="ok" state="completed"/> > <end-cancel g="239,97,48,48" name="bad request"/> > <end-error g="240,154,48,48" name="internal server error"/> > </process> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-388) GPD generates text which is surrunded by tab/newline for action handler's Config Info even if config-type="constructor" or "configuration-property"

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-388?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-388. --------------------------- Resolution: Out of Date > GPD generates text which is surrunded by tab/newline for action handler's Config Info even if config-type="constructor" or "configuration-property" > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: GPD-388 > URL: https://issues.jboss.org/browse/GPD-388 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.7 > Reporter: Toshiya Kobayashi > Assignee: Koen Aers > Priority: Minor > > 1. Create and select a node in GPD editor > 2. Set Action Handler in Properties View > 3. Set "Config Type" SelectBox to "Constructor" or "Compatibility" > 4. Set value like "Test" into the "Config Info" TextArea > 5. See the source xml contains value "Test" surrounded by tab/newline > <action class="ActionHandler" config-type="constructor"> > Test > </action> > On jBPM runtime engine side, config-type="constructor" or "configuration-property" indicates the action handler to take the complete text in xml without trimming [1]. > This leads to unexpected result for users -- even if they understand that config-type="constructor" doesn't trim the text in jBPM runtime, they don't expect that GPD adds tab/newline to the input text. Better behavior would be trimming the input text in TextArea by GPD before passing it to xml. > <action class="ActionHandler" config-type="constructor">Test</action> > [1] http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02/html-single/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-391) Limit assignment operation for Start Task

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-391?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-391. --------------------------- Resolution: Out of Date > Limit assignment operation for Start Task > ----------------------------------------- > > Key: GPD-391 > URL: https://issues.jboss.org/browse/GPD-391 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.7 > Reporter: Toshiya Kobayashi > Assignee: Koen Aers > Priority: Minor > Attachments: assignment_for_start_task.png > > > TaskMgmtInstance#createStartTaskInstance() fills actorId with authenticatedActorId regardless <assignment> settings in <task> in <start-state>. > But currently GPD allows users to assign the start task (e.g. to actor). It's useless and confuses them. See attached screen shot. > So this request is "In case of Start State, only 'Swimlane' should be selectable in Task -> Assignment tab." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-392) Force a transition to have its name in case of Fork

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-392?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-392. --------------------------- Resolution: Out of Date > Force a transition to have its name in case of Fork > --------------------------------------------------- > > Key: GPD-392 > URL: https://issues.jboss.org/browse/GPD-392 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.7, jBPM jPDL Designer 3.2 > Reporter: Toshiya Kobayashi > Assignee: Koen Aers > > When you add transitions from a fork to nodes, GPD omits the name of the first transition. > <fork name="fork1"> > <transition to="node1" ></transition> > <transition to="node2" name="to node2"></transition> > <transition to="node3" name="to node3"></transition> > </fork> > This works without problem. Tokens go to node1, node2, node3. > But, after some modification, you may have a process definition like: > <fork name="fork1"> > <transition to="node1" name="to node1"></transition> > <transition to="node2" ></transition> > <transition to="node3" name="to node3"></transition> > </fork> > In this case, tokens go to node1, node1, node3. > Because if there is a transition without name, the child token goes to default leaving transition (in this case, node1). > This problem may be fixed on jBPM side, but forcing a transition to have its name on GDP side will help users avoid such odd process definition. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

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

8 years, 1 month

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)

8 years, 1 month

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)

8 years, 1 month

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)

8 years, 1 month

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)

8 years, 1 month

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)

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