September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7047) host-elytron.xml, different jvm settings, unnecesarry unsecure interface

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7047?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-7047: ---------------------------------------- Once we reach phase IV of these pull requests I am hoping to completely eliminate these *-elytron.xml configuration files and move Elytron over to the main default configuration of a clean server so for now I don't think it will be beneficial to create forks of the additional host-* files. Phase III may temporarily introduce them as that is where full management integration will come in so they may be application and then depending on what happens in Phase IV we can have a closer look at the default files then. > host-elytron.xml, different jvm settings, unnecesarry unsecure interface > ------------------------------------------------------------------------ > > Key: WFLY-7047 > URL: https://issues.jboss.org/browse/WFLY-7047 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > > host-elytron.xml, different jvm settings, unnecesarry unsecure interface > When I compare host-elytron.xml to host.xml, > 1) jvm settings use permgen element > 2) probably unnecesarry configuration of unsecure profile stays there > Is it worth provide elytron-like host-master/host-slave configuration files for convenience? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-395) Fields for decision handlers are lost

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-395?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-395. --------------------------- Resolution: Out of Date > Fields for decision handlers are lost > ------------------------------------- > > Key: GPD-395 > URL: https://issues.jboss.org/browse/GPD-395 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > Attachments: GPD-395.patch > > > see jBPM-380 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-378) Extend GPD to make it possible to set a task description

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-378?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-378. --------------------------- Resolution: Out of Date > Extend GPD to make it possible to set a task description > -------------------------------------------------------- > > Key: GPD-378 > URL: https://issues.jboss.org/browse/GPD-378 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Environment: not relevant > Reporter: Sebastian Schneider > Assignee: Koen Aers > Labels: description, task > Fix For: jBPM jPDL Designer 4.x > > > At the moment it is not possible to set the task description of a task in the GPD. This is due to 2 things. The task description attribute was forgotten in the jPDL schema definition and there is no field for the description of task when you click on properties in the GPD having a task selected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-389) Add more Items into Eclipse Property View

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-389?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-389. --------------------------- Resolution: Out of Date > Add more Items into Eclipse Property View > ----------------------------------------- > > Key: GPD-389 > URL: https://issues.jboss.org/browse/GPD-389 > Project: jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM jPDL Designer 4.3, jBPM jPDL Designer 4.4 > Environment: JBPM 4.3 Eclipse Plugin > Reporter: Daniel Schaaf > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > Attachments: humanTask-javaTask.patch, transition-condition.patch > > > Hello to the jBOSS Developers Community. > There is a small missing feature in the JBPM GPD Eclipse Plugin, which makes our work together with the business side really hard. The expectation of the business side is to view (and perhaps one time alter) Workflow definitions graphically. To analyse and work with XML Code is not acceptable for them. > Though the Flow Graphs already look impressing, real work on this level is not possible because of the poor functionality of the Properties View. > Out of my point of view it should be a little change to provide here some additional information and functionality, which would bring us forward a big step: > Can you add the following Properties for the Workflow Items: > For Tasks: Form, DueDate, Notification Template; Assignment handler > For Java: A possibility to see and add a variable number of method arguments > For Transitions: Timer duedate (it´s there but only named timer); repeat and condition is missing > For Subprocesses: Parameter in; Parameter out each with var and subvar. > For Java Tasks: arg and field parameters > For Custom Tasks: field parameters > I know, that this set is not complete, but the actual is definitely too small for working and I think the once I suggested to add will enable a better Business Analyst work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-25) Saving processdefinition should add problem markers and entries in problem view if any problems occur

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-25?page=com.atlassian.jira.plugin.sys... ] Koen Aers resolved GPD-25. -------------------------- Resolution: Out of Date > Saving processdefinition should add problem markers and entries in problem view if any problems occur > ----------------------------------------------------------------------------------------------------- > > Key: GPD-25 > URL: https://issues.jboss.org/browse/GPD-25 > 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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GPD-397) Properly initialize the node and the two Connections when a dropping an activity on a connection.

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-397?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-397. --------------------------- Resolution: Out of Date > Properly initialize the node and the two Connections when a dropping an activity on a connection. > ------------------------------------------------------------------------------------------------- > > Key: GPD-397 > URL: https://issues.jboss.org/browse/GPD-397 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > The dropped activity has no name and neither has the first connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

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

9 years, 9 months

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)

9 years, 9 months

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)

9 years, 9 months

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)

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