November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3225) [DMN Designer] Decision table output data type is not stored

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3225?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3225: ------------------------------------- [~manstis] ok, I think it is tightly related to this [~tari_manga]'s [comment|https://github.com/kiegroup/drools/pull/2123#pullrequestreview-17...] > [DMN Designer] Decision table output data type is not stored > ------------------------------------------------------------ > > Key: DROOLS-3225 > URL: https://issues.jboss.org/browse/DROOLS-3225 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-11-01 10-59-08.png, Screenshot from 2018-11-01 15-31-19.png, job-interview.dmn > > > Issue spotted during DROOLS-3214, however probably not related. > If decision table output data type is changed, the change is not reflected in the xml. > Please follow my steps: > - Create new DMN diagram > - Add a decision node > - Set the decision node top level expression as a decision table > - Double click on Output header cell > - Select boolean lets say > - Save the diagram > Check the source, there will be still stored string output data type, like below: > {code:xml} > <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row"> > <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66"> > <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string"> > <dmn:text>input-1</dmn:text> > </dmn:inputExpression> > <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B"> > <dmn:text></dmn:text> > </dmn:inputValues> > </dmn:input> > <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string"> > <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45"> > <dmn:text></dmn:text> > </dmn:outputValues> > <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string"> > <dmn:text></dmn:text> > </dmn:defaultOutputEntry> > </dmn:output> > <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E"> > <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089"> > <dmn:text>"you are right"</dmn:text> > </dmn:inputEntry> > <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string"> > <dmn:text>true</dmn:text> > </dmn:outputEntry> > </dmn:rule> > </dmn:decisionTable> > </dmn:decision> > {code} > But the UI is like: > !Screenshot from 2018-11-01 10-59-08.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2910) [DMN Designer] All grid cell editing should respond to single click

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2910?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2910: ------------------------------------- [~uxdlc] From my point of see no problem in conversion to Story or task. Regarding your question "how to prioritize for 7.3". Well 7.3 is product version and thus planning has to happen via: - BAPL for new features - RHDM, RHPAM for bugs and small enhancements I believe this "single click" affect so many elements of DMN (BPMN, CM probably too) so we need some BAPL jira for this. > [DMN Designer] All grid cell editing should respond to single click > -------------------------------------------------------------------- > > Key: DROOLS-2910 > URL: https://issues.jboss.org/browse/DROOLS-2910 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: UX, UXTeam, drools-tools > > Following from a discussion about https://issues.jboss.org/browse/DROOLS-2874 it was agreed that editing cells (header or body) in the grids should respond to single-click and not double-click. > h2. Manual Acceptance Test > - Not possible edit multiple cells by hold CTRL and click on multiple cells > - Click column/row leading cell discard edit dialog > - Edit can be discarded by escape > - Edit can be discarded by click to canvas > - Invoke edit of cell, return do DRG > - Save and reopen > - Undo redo of editation -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3225) [DMN Designer] Decision table output data type is not stored

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3225?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3225: ------------------------------------- [~manstis] In header cell. > [DMN Designer] Decision table output data type is not stored > ------------------------------------------------------------ > > Key: DROOLS-3225 > URL: https://issues.jboss.org/browse/DROOLS-3225 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-11-01 10-59-08.png, Screenshot from 2018-11-01 15-31-19.png, job-interview.dmn > > > Issue spotted during DROOLS-3214, however probably not related. > If decision table output data type is changed, the change is not reflected in the xml. > Please follow my steps: > - Create new DMN diagram > - Add a decision node > - Set the decision node top level expression as a decision table > - Double click on Output header cell > - Select boolean lets say > - Save the diagram > Check the source, there will be still stored string output data type, like below: > {code:xml} > <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row"> > <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66"> > <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string"> > <dmn:text>input-1</dmn:text> > </dmn:inputExpression> > <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B"> > <dmn:text></dmn:text> > </dmn:inputValues> > </dmn:input> > <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string"> > <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45"> > <dmn:text></dmn:text> > </dmn:outputValues> > <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string"> > <dmn:text></dmn:text> > </dmn:defaultOutputEntry> > </dmn:output> > <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E"> > <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089"> > <dmn:text>"you are right"</dmn:text> > </dmn:inputEntry> > <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string"> > <dmn:text>true</dmn:text> > </dmn:outputEntry> > </dmn:rule> > </dmn:decisionTable> > </dmn:decision> > {code} > But the UI is like: > !Screenshot from 2018-11-01 10-59-08.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4195) CLI/Admin Console does not prompt for a reload after adding a new server-group to server-scoped-roles.

by Chao Wang (Jira)

[ https://issues.jboss.org/browse/WFCORE-4195?page=com.atlassian.jira.plugi... ] Chao Wang moved JBEAP-15759 to WFCORE-4195: ------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4195 (was: JBEAP-15759) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Management (was: Management) Affects Version/s: 7.0.0.Alpha4 (was: 7.1.4.GA) > CLI/Admin Console does not prompt for a reload after adding a new server-group to server-scoped-roles. > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-4195 > URL: https://issues.jboss.org/browse/WFCORE-4195 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 7.0.0.Alpha4 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > CLI/Admin Console does not prompt for a reload after adding a new server-group to server-scoped-roles. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AG-102) Validate timeout attributes in configuration

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-102?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro resolved AG-102. ------------------------------ Resolution: Done > Validate timeout attributes in configuration > --------------------------------------------- > > Key: AG-102 > URL: https://issues.jboss.org/browse/AG-102 > Project: Agroal > Issue Type: Bug > Components: api > Affects Versions: 1.3 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 1.4 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AG-102) Validate timeout attributes in configuration

by Luis Barreiro (Jira)

Luis Barreiro created AG-102: -------------------------------- Summary: Validate timeout attributes in configuration Key: AG-102 URL: https://issues.jboss.org/browse/AG-102 Project: Agroal Issue Type: Bug Components: api Affects Versions: 1.3 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 1.4 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1679) (7.1.z) SASL property com.sun.security.sasl.digest.utf8 does not behave as default when its default value is explicitely configured

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1679?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1679: ---------------------------------- Fix Version/s: 1.1.13.CR1 (was: 1.1.12.CR1) > (7.1.z) SASL property com.sun.security.sasl.digest.utf8 does not behave as default when its default value is explicitely configured > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-1679 > URL: https://issues.jboss.org/browse/ELY-1679 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.11.Final > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > Priority: Major > Fix For: 1.1.13.CR1 > > > SASL property *com.sun.security.sasl.digest.utf8* does not behave as default when its default value is explicitely configured. > When we ommit this explicit property setting then everything is fine. > This property is described here [1] and *true* is default value. Property is defined in wildfly-core project org.wildfly.security.sasl.WildFlySasl.USE_UTF8. > Here is how to set it [2]. > Please check Steps to Reproduce, there is how to update test. > [1] https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_jboss_en... > [2] https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_jboss_en... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1547) SPNEGO: missing negstat field in the first reply for expired token

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1547?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1547: ---------------------------------- Fix Version/s: 1.1.12.CR1 > SPNEGO: missing negstat field in the first reply for expired token > ------------------------------------------------------------------ > > Key: ELY-1547 > URL: https://issues.jboss.org/browse/ELY-1547 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms, HTTP > Affects Versions: 1.2.4.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Major > Fix For: 1.1.12.CR1, 1.3.1.Final, 1.4.0.Final > > > When the client sends an initial SPNEGO token with Kerberos as preferred mechanism and includes an invalid kerberos token, then client expects to see the {{WWW-Authenticate}} HTTP header with SPNEGO response {{negTokenResp[ negState = reject ]}}. > As stated in [SPNEGO specification|https://tools.ietf.org/html/rfc4178#section-4.2.2] negstat is required in first reply: > {code:borderStyle=dashed} > negState > ... > This field is REQUIRED in the first reply from the target, and is > OPTIONAL thereafter. When negState is absent, the actual state > should be inferred from the state of the negotiated mechanism > context. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-386) Unable to create HTTPS connection when some opnessl cipher suite with DHE are used

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-386?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-386: --------------------------------- Fix Version/s: 1.1.12.CR1 > Unable to create HTTPS connection when some opnessl cipher suite with DHE are used > ---------------------------------------------------------------------------------- > > Key: ELY-386 > URL: https://issues.jboss.org/browse/ELY-386 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.0.2.Final > Environment: Oracle java 1.8.0_66 > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Major > Fix For: 1.1.12.CR1, 1.2.0.Beta3 > > > Can't configure OpenSSL cipher suites EXP-DHE-RSA-DES-CBC-SHA, DHE-RSA-DES-CBC-SHA, DHE-RSA-DES-CBC3-SHA, EXP-DHE-DSS-DES-CBC-SHA, DHE-DSS-CBC-SHA, DHE-DSS-DES-CBC3-SHA [1] for HTTPS connection. Seems like everlasting problem DHE vs. EDH [2] - these cipher suites don't work neither in EAP6. IMHO problem is in MechanismDatabase.properties, where these DHE cipher suite are mapped to openssl EDH cipher suite what contradict openssl documentation [1]: > {code} > SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA = alias:TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA > SSL_DHE_RSA_WITH_DES_CBC_SHA = alias:TLS_DHE_RSA_WITH_DES_CBC_SHA > SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA = alias:TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA > TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA = EXP-EDH-RSA-DES-CBC-SHA,DHE,RSA,DES,SHA1,SSLv3,true,EXP40,false,40,56 > TLS_DHE_RSA_WITH_DES_CBC_SHA = EDH-RSA-DES-CBC-SHA,DHE,RSA,DES,SHA1,SSLv3,false,LOW,false,56,56 > TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA = EDH-RSA-DES-CBC3-SHA,DHE,RSA,3DES,SHA1,SSLv3,false,HIGH,true,168,168 > SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA = EXP-EDH-DSS-DES-CBC-SHA,DHE,DSS,DES,SHA1,SSLv3,true,EXP40,false,40,56 > SSL_DHE_DSS_WITH_DES_CBC_SHA = EDH-DSS-DES-CBC-SHA,DHE,DSS,DES,SHA1,SSLv3,false,LOW,false,56,56 > SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA = EDH-DSS-DES-CBC3-SHA,DHE,DSS,3DES,SHA1,SSLv3,false,HIGH,true,168,168 > {code} > Note that MechanismDatabase.properties is inconsistent in mapping DHE cipher suites to openssl cipher suites, as there also exist couple of them which map DHE to DHE, for example > {code} > TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 = DHE-RSA-AES128-SHA256,DHE,RSA,AES128,SHA256,TLSv1.2,false,HIGH,true,128,128 > TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 = DHE-RSA-AES256-SHA256,DHE,RSA,AES256,SHA256,TLSv1.2,false,HIGH,true,256,256 > TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 = DHE-RSA-AES128-GCM-SHA256,DHE,RSA,AES128GCM,AEAD,TLSv1.2,false,HIGH,true,128,128 > TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 = DHE-RSA-AES256-GCM-SHA384,DHE,RSA,AES256GCM,AEAD,TLSv1.2,false,HIGH,true,256,256 > {code} > In MechanismDatabase.properties is also said that > ??Note that all EDH ciphers automatically get a DHE OpenSSL-style alias (and vice-versa)?? > I think this JIRA contradict this comment. > Last thing, based on [1] shouldn't be SSL_DHE_DSS_WITH_DES_CBC_SHA defined as > SSL_DHE_DSS_WITH_DES_CBC_SHA = DHE-DSS-CBC-SHA,DHE,DSS,DES,SHA1,SSLv3,false,LOW,false,56,56 > ? > [1] https://www.openssl.org/docs/manmaster/apps/ciphers.html#CIPHER-SUITE-NAMES > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1123304 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1549) IBM JDK, SPNEGO + FORM; with invalid ticket 401 status code is returned

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1549?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1549: ---------------------------------- Fix Version/s: 1.1.12.CR1 > IBM JDK, SPNEGO + FORM; with invalid ticket 401 status code is returned > ----------------------------------------------------------------------- > > Key: ELY-1549 > URL: https://issues.jboss.org/browse/ELY-1549 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms, HTTP > Affects Versions: 1.2.4.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Major > Labels: ibm-java > Fix For: 1.1.12.CR1, 1.3.1.Final, 1.4.0.Final > > > Given SPNEGO + FORM authentication configuration. AND SPNEGO is SESSION,CONNECTION or default (SESSIN) scoped. And running on IBM java. > When invalid kerberos ticket is send > Then status code 401 is returned with http form. > There is agreement in such case SPNEGO+FORM 200 should return with form. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2018