September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (GPD-330) support ESB attributes and elements

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-330?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-330. --------------------------- Resolution: Out of Date > support ESB attributes and elements > ----------------------------------- > > Key: GPD-330 > URL: https://issues.jboss.org/browse/GPD-330 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > attributes: category, service > elements: part -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-291) Enhance the xml source page

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-291?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-291. --------------------------- Resolution: Out of Date > Enhance the xml source page > --------------------------- > > Key: GPD-291 > URL: https://issues.jboss.org/browse/GPD-291 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > - Code completion for class attributes > - Errors shown in problems view (cfr GPD-288) when invalid values are given (e.g. unexisting class, unexisting node name) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-234) Two Nodes with the same name

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-234?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-234. --------------------------- Resolution: Out of Date > Two Nodes with the same name > ---------------------------- > > Key: GPD-234 > URL: https://issues.jboss.org/browse/GPD-234 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.3 > Environment: Eclipse 3.3.2 > Reporter: Sven Daumann > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.x > > > step1: Create a Node and put a transition to this Node. > step2: Rename the Node and use the name of an existing Node. > The GPD show both Nodes with Transitions. > step3: Close the diagram > step4: Reopen the diagram > problem: Only one Node is visible, the two transitions go to the one Node. > step5: Move the Node. The moving Node has no transition. Under the moved Node, the other Node is now visible, with both transitions. > During rename, there is no warning, that another Node with the same name exist. > The XML data contains two Nodes. > processdefinition.xml > <?xml version="1.0" encoding="UTF-8"?> > <process-definition xmlns="" name="Test"> > <start-state name="start-state1"> > <transition to="node1" name="startet"></transition> > </start-state> > <node name="node1"> > <transition to="node2" name="ok"></transition> > <transition to="Test" name="toTest"></transition> > </node> > <node name="node2"> > <transition to="end-state1" name="ok"></transition> > <transition to="Test" name="toTest"></transition> > </node> > <task-node name="Test"></task-node> > <task-node name="Test"></task-node> > <end-state name="end-state1"></end-state> > </process-definition> > gpd.xml > <?xml version="1.0" encoding="UTF-8"?> > <root-container name="Test" width="675" height="634"> > <node name="start-state1" x="375" y="272" width="132" height="36"> > <edge> > <label x="5" y="-10"/> > </edge> > </node> > <node name="node1" x="374" y="353" width="132" height="36"> > <edge> > <label x="5" y="-10"/> > </edge> > <edge> > <label x="5" y="-10"/> > </edge> > </node> > <node name="node2" x="378" y="448" width="132" height="36"> > <edge> > <label x="5" y="-10"/> > </edge> > <edge> > <label x="5" y="-10"/> > </edge> > </node> > <node name="end-state1" x="383" y="548" width="132" height="36"/> > <node name="Test" x="172" y="347" width="132" height="36"/> > <node name="Test" x="174" y="451" width="132" height="36"/> > </root-container> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GPD-337) image clipping

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/GPD-337?page=com.atlassian.jira.plugin.sy... ] Koen Aers resolved GPD-337. --------------------------- Resolution: Out of Date > image clipping > -------------- > > Key: GPD-337 > URL: https://issues.jboss.org/browse/GPD-337 > Project: jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Tom Baeyens > Assignee: Koen Aers > Priority: Minor > Fix For: jBPM jPDL Designer 4.x > > > the generated images are too large. clipping them would be nice to have. > watch out with clipping the top left corner (i assume that is coordinates 0,0). if you clip that while saving the image, then the coordinates in the process, used by the console might be affected. > while clipping the bottom right corner should be possible without problem for the console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7045) domain-elytron.xml, missing singelton subsystem, different ejb cache type

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7045?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-7045: ---------------------------------------- On the EJB3 subsystem it turns out the includes ordering needed reversing for the Elytron configuration. Changes applied to this branch ready to be bundled in a PR upstream: - https://github.com/wildfly-security-incubator/wildfly/tree/elytron_phase_I > domain-elytron.xml, missing singelton subsystem, different ejb cache type > ------------------------------------------------------------------------- > > Key: WFLY-7045 > URL: https://issues.jboss.org/browse/WFLY-7045 > 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 > > > When I compare domain-elytron.xml to domain.xml, > 1) There is missing org.wildfly.extension.clustering.singleton extension installed. > 2) There is changed ejb cache configuration > 1254c1129 > < <stateful default-access-timeout="5000" cache-ref="simple" passivation-disabled-cache-ref="simple"/> > --- > > <stateful default-access-timeout="5000" cache-ref="distributable" passivation-disabled-cache-ref="simple"/> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7045) domain-elytron.xml, missing singelton subsystem, different ejb cache type

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7045?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-7045: ---------------------------------------- >From what I can see the latter appears to be a bug in feature pack assembly. The EJB3 Subsystem is defined as: - {code:xml} <subsystem supplement="ha-elytron">ejb3.xml</subsystem> {code} In the subsystem this is defined as: - {code:xml} <supplement name="ha-elytron" includes="ha elytron"/> {code} These in turn are defined as : - {code:xml} <supplement name="ha"> <replacement placeholder="STATEFUL-BEAN"> <stateful default-access-timeout="5000" cache-ref="distributable" passivation-disabled-cache-ref="simple"/> </replacement> </supplement> <supplement name="elytron" includes="default"> <replacement placeholder="ELYTRON"> <application-security-domains> <application-security-domain name="other" security-domain="ApplicationDomain"/> </application-security-domains> </replacement> </supplement> {code} But default is defines as: - {code:xml} <supplement name="default"> <replacement placeholder="STATEFUL-BEAN"> <stateful default-access-timeout="5000" cache-ref="simple" passivation-disabled-cache-ref="simple"/> </replacement> </supplement> {code} So somehow the replacement defined in default is used instead of the one defined in ha. > domain-elytron.xml, missing singelton subsystem, different ejb cache type > ------------------------------------------------------------------------- > > Key: WFLY-7045 > URL: https://issues.jboss.org/browse/WFLY-7045 > 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 > > > When I compare domain-elytron.xml to domain.xml, > 1) There is missing org.wildfly.extension.clustering.singleton extension installed. > 2) There is changed ejb cache configuration > 1254c1129 > < <stateful default-access-timeout="5000" cache-ref="simple" passivation-disabled-cache-ref="simple"/> > --- > > <stateful default-access-timeout="5000" cache-ref="distributable" passivation-disabled-cache-ref="simple"/> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1270) support fact handle operations for REST APIs on kie server

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1270?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1270: ---------------------------------- Component/s: core engine > support fact handle operations for REST APIs on kie server > ---------------------------------------------------------- > > Key: DROOLS-1270 > URL: https://issues.jboss.org/browse/DROOLS-1270 > Project: Drools > Issue Type: Enhancement > Components: core engine, kie server > Affects Versions: 6.5.0.CR1 > Environment: kie server > Reporter: Dan Cimpoesu > Assignee: Mario Fusco > Fix For: 6.5.0.Final > > > Please support fact handle operations for REST APIs on kie server. > Fact handle operations are currently not supported in kie server as they usually bring less value in rule based systems where most of the operations are stateless. Though they do provide rather big value for processes integrated with rules. > Operations that require fact handles are: > - delete facts > - update facts -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7044) standalone-elytron.xml , unnecessary unsecure interface

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7044?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-7044: ---------------------------------------- Changes applied to this branch ready to be bundled in a PR upstream: - https://github.com/wildfly-security-incubator/wildfly/tree/elytron_phase_I > standalone-elytron.xml , unnecessary unsecure interface > ------------------------------------------------------- > > Key: WFLY-7044 > URL: https://issues.jboss.org/browse/WFLY-7044 > 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 > > > When I compare standalone-elytron.xml to standalone.xml, there is additional section > {noformat} > </interface> >  > <interface name="unsecure"> >  > <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/> > {noformat} > Is it necessary? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1270) support fact handle operations for REST APIs on kie server

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1270?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1270: ------------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > support fact handle operations for REST APIs on kie server > ---------------------------------------------------------- > > Key: DROOLS-1270 > URL: https://issues.jboss.org/browse/DROOLS-1270 > Project: Drools > Issue Type: Enhancement > Components: kie server > Affects Versions: 6.5.0.CR1 > Environment: kie server > Reporter: Dan Cimpoesu > Assignee: Mario Fusco > Fix For: 6.5.0.Final > > > Please support fact handle operations for REST APIs on kie server. > Fact handle operations are currently not supported in kie server as they usually bring less value in rule based systems where most of the operations are stateless. Though they do provide rather big value for processes integrated with rules. > Operations that require fact handles are: > - delete facts > - update facts -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[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 updated WFLY-7047: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > 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, 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