February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4261) Update Maven dependencies to reference individual Elytron modules.

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFCORE-4261?page=com.atlassian.jira.plug... ] Ranabir Chakraborty commented on WFCORE-4261: --------------------------------------------- [~dlofthouse] Can you please elaborate this issue ? > Update Maven dependencies to reference individual Elytron modules. > ------------------------------------------------------------------ > > Key: WFCORE-4261 > URL: https://issues.redhat.com/browse/WFCORE-4261 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Priority: Major > > Additionally remove the root 'wildfly-elytron' dependency. > This should also review the classes the application server users as we will likely want to start considering these public API. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5053) Clean up kie-wb-common-server-ui-client unused dependencies

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5053: ----------------------------------- Summary: Clean up kie-wb-common-server-ui-client unused dependencies Key: DROOLS-5053 URL: https://issues.redhat.com/browse/DROOLS-5053 Project: Drools Issue Type: Task Components: kie server Reporter: Jozef Marko Assignee: Jozef Marko There are unused dependencies in the module {{kie-wb-common-server-ui-client}} found by {{mvn dependency:analyze}}. h2. Acceptance test - Full downstream build passed - manually checked produced wars -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5051) Mvel type coercion and rounding behavior compatibility between mvel 2.2.8 and 2.4.3

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5051?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5051: -------------------------------------- Sprint: 2020 Week 07-09 (from Feb 10) > Mvel type coercion and rounding behavior compatibility between mvel 2.2.8 and 2.4.3 > ----------------------------------------------------------------------------------- > > Key: DROOLS-5051 > URL: https://issues.redhat.com/browse/DROOLS-5051 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.33.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > Labels: support > > I have rule like as: > ========= > rule "My Rule" > no-loop true > dialect "mvel" > when > $info : MyInfo() > then > modify ($info) { > setResult(15 * Math.round( new BigDecimal("49.4") ) / 100 ) > } > end > ========= > If I execute this rule in BRMS 6.4.x release (mvel 2.2.8), I will get 7.35 in the response . But if I execute same rule in RHDM 7.4.+ release (mvel 2.4.3) I will 7 in the response. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5052) Remote kie container version overlays with the url

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5052: ----------------------------------- Summary: Remote kie container version overlays with the url Key: DROOLS-5052 URL: https://issues.redhat.com/browse/DROOLS-5052 Project: Drools Issue Type: Bug Components: kie server Affects Versions: 7.34.0.Final Reporter: Jozef Marko Assignee: Jozef Marko Attachments: Screenshot from 2020-02-12 10-15-11.png, Screenshot from 2020-02-12 10-18-37.png The version of the remote container overlays with the url of container. See the attached screenshot [1]. The proposed fix changes the rendering to [2]. [1] !Screenshot from 2020-02-12 10-15-11.png|thumbnail! [2] !Screenshot from 2020-02-12 10-18-37.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4172) Add support for TLS 1.3

by Harish Murali (Jira)

[ https://issues.redhat.com/browse/WFCORE-4172?page=com.atlassian.jira.plug... ] Harish Murali edited comment on WFCORE-4172 at 2/12/20 3:41 AM: ---------------------------------------------------------------- [~fjuma] Can you let me know the wildfly version from where this is available. I can see only the elytron version here. Is this available only in wildfly 19? We are using wildfly version 17. If I manually merge this commit to wildfly 17 (only locally), what are the chances that it is going to work there. was (Author: harishjboss1): [~fjuma] Can you let me know the wildfly version from where this is available. I can see the elytron version here. Is this available only in wildfly 19? We are using wildfly version 17. If I manually merge this commit to wildfly 17 (only locally), what are the chances that it is going to work there. > Add support for TLS 1.3 > ----------------------- > > Key: WFCORE-4172 > URL: https://issues.redhat.com/browse/WFCORE-4172 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Labels: affects-model, eap-7.2.0-deferred > Fix For: 11.0.0.Beta6 > > > It presently appears as though TLS 1.3 support could be available from Java 11. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4172) Add support for TLS 1.3

by Harish Murali (Jira)

[ https://issues.redhat.com/browse/WFCORE-4172?page=com.atlassian.jira.plug... ] Harish Murali commented on WFCORE-4172: --------------------------------------- [~fjuma] Can you let me know the wildfly version from where this is available. I can see the elytron version here. Is this available only in wildfly 19? We are using wildfly version 17. If I manually merge this commit to wildfly 17 (only locally), what are the chances that it is going to work there. > Add support for TLS 1.3 > ----------------------- > > Key: WFCORE-4172 > URL: https://issues.redhat.com/browse/WFCORE-4172 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Labels: affects-model, eap-7.2.0-deferred > Fix For: 11.0.0.Beta6 > > > It presently appears as though TLS 1.3 support could be available from Java 11. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10388) Persistent EJB timer timed_object_id naming discrepancy

by Lukas Vydra (Jira)

[ https://issues.redhat.com/browse/WFLY-10388?page=com.atlassian.jira.plugi... ] Lukas Vydra reassigned WFLY-10388: ---------------------------------- Assignee: Lukas Vydra > Persistent EJB timer timed_object_id naming discrepancy > ------------------------------------------------------- > > Key: WFLY-10388 > URL: https://issues.redhat.com/browse/WFLY-10388 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 12.0.0.Final > Reporter: Boris Pran > Assignee: Lukas Vydra > Priority: Major > > Persistent EJB timers created declaratively (with @Schedule) create timed_object_id without version information while timers created using TimerService API include version info from deployment unit. > This way after version upgrade @Schedule timers survive but TimerService API created ones are lost and need to be created again. > I also seems that old timers remain created or at least their definitions can be seen in jboss_ejb_timer table. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12797) WFLY quickstart 'jts' contains errors after import into Code Ready in the 'jboss-ejb3.xml' file

by Sudeshna Sur (Jira)

[ https://issues.redhat.com/browse/WFLY-12797?page=com.atlassian.jira.plugi... ] Sudeshna Sur commented on WFLY-12797: ------------------------------------- [~ochaloup] Can I assign this to me, as I have already sent a new pull request? https://github.com/wildfly/quickstart/pull/376 > WFLY quickstart 'jts' contains errors after import into Code Ready in the 'jboss-ejb3.xml' file > ----------------------------------------------------------------------------------------------- > > Key: WFLY-12797 > URL: https://issues.redhat.com/browse/WFLY-12797 > Project: WildFly > Issue Type: Bug > Components: Quickstarts, Transactions > Affects Versions: 18.0.1.Final > Environment: OS X 10.14.5 > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > h1. *The "jboss-ejb3.xml" file in the EAP "jts" quickstart contains the following 2 errors:* > * cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:ejb-name'. One of '{"http://java.sun.com/xml/ns/javaee":description, "http://java.sun.com/xml/ns/javaee":ejb-name}' is expected. > * Referenced file contains errors (jar:file:/Applications/codereadystudio-eap-8/studio/codereadystudio.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.7.0.v20190624-1620.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > h2. Red Hat CodeReady Studio version: 12.12.0.GA -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5051) Mvel type coercion and rounding behavior compatibility between mvel 2.2.8 and 2.4.3

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5051?page=com.atlassian.jira.plug... ] Toshiya Kobayashi edited comment on DROOLS-5051 at 2/11/20 11:08 PM: --------------------------------------------------------------------- https://github.com/mvel/mvel/commit/dd59667d693a776ca46bf61f3e19293f6913ee1f https://github.com/mvel/mvel/commit/e2f51fcb > Mvel type coercion and rounding behavior compatibility between mvel 2.2.8 and 2.4.3 > ----------------------------------------------------------------------------------- > > Key: DROOLS-5051 > URL: https://issues.redhat.com/browse/DROOLS-5051 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.33.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > Labels: support > > I have rule like as: > ========= > rule "My Rule" > no-loop true > dialect "mvel" > when > $info : MyInfo() > then > modify ($info) { > setResult(15 * Math.round( new BigDecimal("49.4") ) / 100 ) > } > end > ========= > If I execute this rule in BRMS 6.4.x release (mvel 2.2.8), I will get 7.35 in the response . But if I execute same rule in RHDM 7.4.+ release (mvel 2.4.3) I will 7 in the response. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5051) Mvel type coercion and rounding behavior compatibility between mvel 2.2.8 and 2.4.3

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5051?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5051: -------------------------------------- Description: I have rule like as: ========= rule "My Rule" no-loop true dialect "mvel" when $info : MyInfo() then modify ($info) { setResult(15 * Math.round( new BigDecimal("49.4") ) / 100 ) } end ========= If I execute this rule in BRMS 6.4.x release (mvel 2.2.8), I will get 7.35 in the response . But if I execute same rule in RHDM 7.4.+ release (mvel 2.4.3) I will 7 in the response. was: I have rule like as: ========= rule "My Rule" no-loop true dialect "mvel" when $info : MyInfo() then modify ($info) { setResult(15 * Math.round( new BigDecimal("49.4") ) / 100 ) } end ========= If I exeucte this rule in BRMS 6.4.x release, I will get 7.35 in the reponse . But if I execute same rule in RHDM 7.4.+ release I will 7 in the response. > Mvel type coercion and rounding behavior compatibility between mvel 2.2.8 and 2.4.3 > ----------------------------------------------------------------------------------- > > Key: DROOLS-5051 > URL: https://issues.redhat.com/browse/DROOLS-5051 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.33.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > Labels: support > > I have rule like as: > ========= > rule "My Rule" > no-loop true > dialect "mvel" > when > $info : MyInfo() > then > modify ($info) { > setResult(15 * Math.round( new BigDecimal("49.4") ) / 100 ) > } > end > ========= > If I execute this rule in BRMS 6.4.x release (mvel 2.2.8), I will get 7.35 in the response . But if I execute same rule in RHDM 7.4.+ release (mvel 2.4.3) I will 7 in the response. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 February 2020