September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (GPD-232) add "binding" attribute to model class of subprocess in process designer

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-232?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-232. --------------------------- Resolution: Out of Date > add "binding" attribute to model class of subprocess in process designer > ------------------------------------------------------------------------ > > Key: GPD-232 > URL: https://issues.jboss.org/browse/GPD-232 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Environment: probably not important here, but: windows XP java 1.6 > Reporter: s p > Assignee: Koen Aers > Priority: Minor > Labels: attribute, binding, designer, gpd, late, model > Fix For: jBPM jPDL Designer 3.2 > > Attachments: supportBindingAttributeInSubprocess.path, supportBindingAttributeInSubprocess.path > > > There is optional attribute binding in SubProcess element, but it's not accessible from GPD, becouse in model of subprocess it isn't supported. > It would be nice to add it to model and to xmladapter classes, to allow people access to this attribute from their extensions of process designer. > At least it would be very usefull to me :) > I've attached a patch (updated - the bigger is wrong i it changes formatting, use the smaller (newer) file). > I use version 3.2.3 from svn of jbpm and it isn't in combo, so I've choosed unknow version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-158) Have the formsgenerator put a required attribute on jsf components

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-158?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-158. --------------------------- Resolution: Out of Date > Have the formsgenerator put a required attribute on jsf components > ------------------------------------------------------------------ > > Key: GPD-158 > URL: https://issues.jboss.org/browse/GPD-158 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM JPDL Designer 3.1.0.CR > Reporter: James Baxter > Assignee: Koen Aers > Priority: Minor > Fix For: jBPM jPDL Designer 3.x > > > Tasks can have variables specified as 'required'. This is not built into the taskform, the forms are missing the following attribute from the h:input tag: > [code] > required="true" > [/code] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-307) make g the last attribute

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-307?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-307. --------------------------- Resolution: Out of Date > make g the last attribute > ------------------------- > > Key: GPD-307 > URL: https://issues.jboss.org/browse/GPD-307 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Tom Baeyens > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > koen, could you check if it is easy to make g the last attribute ? currently it seems to be systematically the first attribute. > <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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-366) Process Definition not displayed correctly if xml is updated directly

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-366?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-366. --------------------------- Resolution: Out of Date > Process Definition not displayed correctly if xml is updated directly > --------------------------------------------------------------------- > > Key: GPD-366 > URL: https://issues.jboss.org/browse/GPD-366 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.2 > Environment: Windows Vista, Eclispe 3.4.2 , JBPM 3.2.1 > Reporter: TejJBPM > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.x > > > Whenever I edit the processdefinition.xml directly for example ( I add a mail action class)..the original display in the processdefinition goes strange. IT loses all the transitions. > This does not happen always. But intermittenly. Because of this whenever i change the xml file i save it and cross check it in the display whether everything is fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-35) enhancement drawing transitions

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-35?page=com.atlassian.jira.plugin.sys... ] Koen Aers resolved GPD-35. -------------------------- Resolution: Out of Date > enhancement drawing transitions > ------------------------------- > > Key: GPD-35 > URL: https://issues.jboss.org/browse/GPD-35 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > When the mousepointer is in the outer area of a node/state/task/.... but within it's boundaries, it should be possible to draw a transition. This is makes using the gpd a lot faster (not switching in the toolbar) > Maybe it should only be in the 'middle areas' of top, bottom, left and right and not the corners -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-305) GPD diagram are not in sync with text.

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-305?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-305. --------------------------- Resolution: Out of Date > GPD diagram are not in sync with text. > -------------------------------------- > > Key: GPD-305 > URL: https://issues.jboss.org/browse/GPD-305 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.6, jBPM jPDL Designer 3.1.7 > Reporter: Andrey Sobolev > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.x > > > Hi, > We found a problem then try to use GPD from our product. > Editor could be not in sync with diagram if eclipse file are changed then editor are opened. > With following simple scenario problem could be reproduced: > 1) Create new empty JPDL document. > Content will be following: > <?xml version="1.0" encoding="UTF-8"?> > <process-definition xmlns="" name="test"></process-definition> > 2)Then open processdefinition.xml file with generic text editor and change content to: > <?xml version="1.0" encoding="UTF-8"?> > <process-definition xmlns="" name="test"/> > 3) After text is saved. Source and diagram are not in sync. So then we add new elements, text are not modified. > Best regards, > Andrei. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-296) savnig problem on Persian/Arabic characters

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-296?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-296. --------------------------- Resolution: Out of Date > savnig problem on Persian/Arabic characters > ------------------------------------------- > > Key: GPD-296 > URL: https://issues.jboss.org/browse/GPD-296 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.5 > Reporter: mahdi asgari nea > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.x > > > Hi dear Help Desk > I have a problem to save process designer in Persian/Arabic language. > The process save correctly but when i reopen the process all tasks and nodes positions are bollixed but the names are saved correct. > In the gpd.xml file the task and node names saved like ????? symbols. > Is there any solution or configuration to fix this problem? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-299) The GUI does not support exception handling of invoked ESB services

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-299?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-299. --------------------------- Resolution: Out of Date > The GUI does not support exception handling of invoked ESB services > ------------------------------------------------------------------- > > Key: GPD-299 > URL: https://issues.jboss.org/browse/GPD-299 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.5 > Reporter: Jiri Pechanec > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.x > > > See the linked doc for the implementation > http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.GA/html-single/Se... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-193) Add the ability to drag new components into the workflow

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-193?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-193. --------------------------- Resolution: Out of Date > Add the ability to drag new components into the workflow > -------------------------------------------------------- > > Key: GPD-193 > URL: https://issues.jboss.org/browse/GPD-193 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Reporter: Gunnar Hillert > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > In the workflow designer it would be nice if I could simply drag a new workflow component into the main workflow. > Right now you have to select the component from the component palette and then click again in the main workflow area to place the component. This seems to be slightly less intuitive than just drag-and-drop the new component into the workflow. > Also, it would be great if I could then drag a component from the palette onto an existing 'transition line' and the transition will automatically connect to the newly placed component. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-230) GenericElements don't update their attributes when changed from xml editor

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-230?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-230. --------------------------- Resolution: Out of Date > GenericElements don't update their attributes when changed from xml editor > -------------------------------------------------------------------------- > > Key: GPD-230 > URL: https://issues.jboss.org/browse/GPD-230 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Reporter: Marcin Slusarz > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.2 > > Attachments: GenericElementXmlAdapter.java.diff > > > If I modify any attribute of tag (represented as GenericElement) in XML source and switch back to "Diagram" tab, these changes are not propagated to GenericElements (only value of tag is updated). > I found that GenericElementXmlAdapter.doModelUpdate reacts only to "#text" changes... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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