September 2016 - jboss-jira - Jboss List Archives

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

8 years, 1 month

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)

8 years, 1 month

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)

8 years, 1 month

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)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-231) Editing task node's name in source view breaks XML, if node is used.

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-231?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-231. --------------------------- Resolution: Out of Date > Editing task node's name in source view breaks XML, if node is used. > -------------------------------------------------------------------- > > Key: GPD-231 > URL: https://issues.jboss.org/browse/GPD-231 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.3.SP2 > Environment: Windows XP SP3, Eclipse 3.3 > Reporter: N/A N/A > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.x > > > When switching to source code view and manually editing a task node's name which is used by an existing transition, breaks the XML. You can enter whatever you like, but the task's name attribute stays the same while the transition's to-attribute is cluttered with parts of the characters you have enter. Depending on whether you use backspace, the cursor may also jump around in the document, erasing some unrelated code. > Here is an example: > BEFORE > <start-state name="First step"> > <task name="First step" swimlane="Role"> > <controller> > <variable access="read,write,required" name="someVar" mapped-name="Some Var"/> > </controller> > </task> > <transition to="Second step"/> > </start-state> > <task-node name="Second Step">  > <task name="Second Step" swimlane="Second role"> > <controller> > <variable access="read,write,required" name="someOtherVar" mapped-name="Some Other Var"/> > </controller> > </task> > <transition to="Third step"/> > </task-node> > AFTER > <start-state name="First step"> > <task name="First step" swimlane="Role"> > <controller> > <variable access="read,write,required" name="someVar" mapped-name="Some Var"/> > </controller> > </task> > <transition to="Second"/>  > </start-state> > <task-node name="Second Ste>  > <task nme="Second Step" swimlane="Second role">  > <controller> > <variable access="read,write,required" name="someOtherVar" mapped-name="Some Other Var"/> > </controller> > </task> > <transition to="Third step"/> > </task-node> > Another option is adding something to the node's name... First look at the original once more, when trying to add " Part 1" to "Second Step" (so it should be Second Step Part 1) we get this as the result: > <start-state name="First step"> > <task name="First step" swimlane="Role"> > <controller> > <variable access="read,write,required" name="someVar" mapped-name="Some Var"/> > </controller> > </task> > <transition to="Second step Part 1"/>  > </start-state> > <task-node name="Second Step">  > <task name="Second Step" swimlane="Second role"> > <controller> > <variable access="read,write,required" name="someOtherVar" mapped-name="Some Other Var"/> > </controller> > </task> > <transition to="Third step"/> > </task-node> > This can be worked around by first changing the transition's to-attribute to something that isn't used, but it's nonetheless a bug which causes some grief. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-176) Add code completion inside attributes and values within the xml source

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-176?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-176. --------------------------- Resolution: Out of Date > Add code completion inside attributes and values within the xml source > ---------------------------------------------------------------------- > > Key: GPD-176 > URL: https://issues.jboss.org/browse/GPD-176 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-243) Cannot browse services while adding ESB Node

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-243?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-243. --------------------------- Resolution: Out of Date > Cannot browse services while adding ESB Node > -------------------------------------------- > > Key: GPD-243 > URL: https://issues.jboss.org/browse/GPD-243 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.4 > Reporter: Piotr Hrebieniuk > Assignee: Koen Aers > Labels: ESB_node, services, xml > Fix For: jBPM jPDL Designer 3.x > > > The ESB type node is used to tell the process, that the logic of this node is defined in ESB service body. But, unfortunately, we cannot choose between services defined in nearest esb file (or referenced somewhere in process definition). > What it causes, is that every time someone want to model a process, he has to search xml file. I suggest adding some kind of browser, it should be easy to implement with any xml parser. > P.S.: i could do it, if Koen doesn't have much time.. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-112) Super state node name is not displayed

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-112?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-112. --------------------------- Resolution: Out of Date > Super state node name is not displayed > -------------------------------------- > > Key: GPD-112 > URL: https://issues.jboss.org/browse/GPD-112 > Project: jBPM GPD > Issue Type: Sub-task > Components: jpdl > Environment: all > Reporter: vladimir mezhibovsky > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.x > > > Having a name of the super state shown on the process diagram would really help. Currently it is only visible in the outline window which make it hard to understand the process by just looking on the diagram. You have to click on the rectangle that represent super state to see the name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-177) Add code completion in the text input fields on the properties view

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-177?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-177. --------------------------- Resolution: Out of Date > Add code completion in the text input fields on the properties view > ------------------------------------------------------------------- > > Key: GPD-177 > URL: https://issues.jboss.org/browse/GPD-177 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GPD-155) secure the gpd deployment servlet

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-155?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-155. --------------------------- Resolution: Out of Date > secure the gpd deployment servlet > --------------------------------- > > Key: GPD-155 > URL: https://issues.jboss.org/browse/GPD-155 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Tom Baeyens > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.x > > > the gpd deployment servlet should be secured. the gpd should add authentication information in the url like e.g. http://gpd:gpd:localhost/jbpm-console/upload or something like that. then the users will be able to control the authorization through the web interface itself. -- 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