March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1705) Audit remaining Class.forName in static factory methods

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-1705?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-1705: -------------------------------------- Assignee: Edoardo Vacchi (was: Matteo Mortari) > Audit remaining Class.forName in static factory methods > ------------------------------------------------------- > > Key: DROOLS-1705 > URL: https://issues.jboss.org/browse/DROOLS-1705 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Matteo Mortari > Assignee: Edoardo Vacchi > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3736) DMN DT Analysis Table Completeness

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3736?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3736: ----------------------------------- Story Points: 3 (was: 2) > DMN DT Analysis Table Completeness > ---------------------------------- > > Key: DROOLS-3736 > URL: https://issues.jboss.org/browse/DROOLS-3736 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Gaps in relation with Hit Policy -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3737) DMN DT Analysis Table Consistency

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3737?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3737: ----------------------------------- Story Points: 3 (was: 2) > DMN DT Analysis Table Consistency > --------------------------------- > > Key: DROOLS-3737 > URL: https://issues.jboss.org/browse/DROOLS-3737 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Table Consistency in relation with Hit Policy -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2769) callback methods for: before/after invoke BKM/DS

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-2769?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-2769: ----------------------------------- Story Points: 2 (was: 3) > callback methods for: before/after invoke BKM/DS > ------------------------------------------------ > > Key: DROOLS-2769 > URL: https://issues.jboss.org/browse/DROOLS-2769 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > {quote}As part of another feature, I would like to create callback methods for both "before/after invoke BKM/DS", so that we can report on actual execution of BKMs and Decision Services. But this is a conversation for another day.{quote} > Ref https://github.com/kiegroup/drools/pull/1986#discussion_r204029977 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3738) DMN DT Analysis cover Boolean data type

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3738?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3738: ----------------------------------- Story Points: 2 (was: 1) > DMN DT Analysis cover Boolean data type > --------------------------------------- > > Key: DROOLS-3738 > URL: https://issues.jboss.org/browse/DROOLS-3738 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Extend DMN DT Analysis to manage Boolean data type -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11824) WildFly Operator for Kubernetes/OpenShift

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-11824?page=com.atlassian.jira.plugin... ] Jeff Mesnil moved EAP7-1224 to WFLY-11824: ------------------------------------------ Project: WildFly (was: EAP 7 Planning Pilot) Key: WFLY-11824 (was: EAP7-1224) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Server (was: OpenShift) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.3.0.GA) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > WildFly Operator for Kubernetes/OpenShift > ----------------------------------------- > > Key: WFLY-11824 > URL: https://issues.jboss.org/browse/WFLY-11824 > Project: WildFly > Issue Type: Feature Request > Components: Server > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > > WildFly Operator for OpenShift / Kubernetes > The Operator will simplify configuring and deploying WildFly applications at a scale. > The Operator will let user perform administration tasks including but not limited to: > - start up WildFly Server cluster with a given number of nodes and a deployed application > - make web applications reachable from outside > - as new image updates available in the RHCC (due to recent CVEs, CPs, etc.) apply this recent image to the EAP containers. > - configure full standalone.xml file for OpenShift or via ConfigMap provide a custom (users' own) standalone configuration -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11824) WildFly Operator for Kubernetes/OpenShift

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-11824?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-11824: ------------------------------- Labels: (was: EAP-CD18) > WildFly Operator for Kubernetes/OpenShift > ----------------------------------------- > > Key: WFLY-11824 > URL: https://issues.jboss.org/browse/WFLY-11824 > Project: WildFly > Issue Type: Feature Request > Components: Server > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > > WildFly Operator for OpenShift / Kubernetes > The Operator will simplify configuring and deploying WildFly applications at a scale. > The Operator will let user perform administration tasks including but not limited to: > - start up WildFly Server cluster with a given number of nodes and a deployed application > - make web applications reachable from outside > - as new image updates available in the RHCC (due to recent CVEs, CPs, etc.) apply this recent image to the EAP containers. > - configure full standalone.xml file for OpenShift or via ConfigMap provide a custom (users' own) standalone configuration -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11818) wildfly-16.0.0.Final: "From address" is no more used as default from in email

by Wolfgang Mayer (Jira)

[ https://issues.jboss.org/browse/WFLY-11818?page=com.atlassian.jira.plugin... ] Wolfgang Mayer commented on WFLY-11818: --------------------------------------- Jaikiran, as mentioned in the mvn output above it is: Java version: 11.0.2, vendor: Oracle Corporation. java -version java version "11.0.2" 2019-01-15 LTS Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS) Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode) > wildfly-16.0.0.Final: "From address" is no more used as default from in email > ----------------------------------------------------------------------------- > > Key: WFLY-11818 > URL: https://issues.jboss.org/browse/WFLY-11818 > Project: WildFly > Issue Type: Bug > Components: Mail > Affects Versions: 16.0.0.Final > Environment: mvn -v > Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T20:41:47+02:00) > Maven home: /apps/apache-maven-3.6.0 > Java version: 11.0.2, vendor: Oracle Corporation, runtime: /usr/java/jdk-11.0.2 > Default locale: de_DE, platform encoding: UTF-8 > OS name: "linux", version: "4.12.14-lp150.12.48-default", arch: "amd64", family: "unix" > Reporter: Wolfgang Mayer > Assignee: Tomaz Cerar > Priority: Major > > As mentioned in the Help (description) of 'Mail Session' configuration: > From: *From address that is used as default from, if not set when sending* > Apparently this is not the case anymore in wildfly-16.0.0.Final. > For example I made a test with quickstart-16.0/mail/. > When omitting the line > *message.setFrom(new InternetAddress(from));* > Sending mail fails with: > com.sun.mail.smtp.SMTPSendFailedException: 554-Transaction failed > 554 Unauthorized sender address. > I have the same issue when replacing the line above with > message.setFrom(new InternetAddress()); > I am pretty sure that this is working in wildfly-15 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1761) Unicode normalization in SASL client breaks some non-ASCII passwords

by Philippe Marschall (Jira)

[ https://issues.jboss.org/browse/ELY-1761?page=com.atlassian.jira.plugin.s... ] Philippe Marschall updated ELY-1761: ------------------------------------ Steps to Reproduce: * Connect a WildFly to an Active Directory instance using the LDAP realm. * Set your Active Directory password to something with a diaeresis (¨) eg. "aaaaaa¨". Do not use a composed character like ä, as far as we can tell they are working. * Try to log in to WildFly using something that uses SASL, eg. remote EJB. was: * Connect a WildFly to an Active Directory instance using the LDAP realm. * Set your Active Directory password to something with a diaeresis (¨) "aaaaaa¨". Do not use a composed character like ä, as far as we can tell they are working. * Try to log in to WildFly using something that uses SASL, eg. remote EJB. > Unicode normalization in SASL client breaks some non-ASCII passwords > -------------------------------------------------------------------- > > Key: ELY-1761 > URL: https://issues.jboss.org/browse/ELY-1761 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Affects Versions: 1.7.0.Final > Reporter: Philippe Marschall > Priority: Major > > We have users that use U+00A8 ([diaeresis|https://en.wikipedia.org/wiki/Diaeresis_(diacritic)]) as an Active Directory password. They can not log in using the Elytron LDAP realm. Here's the sequence of events: > * PlainSaslClient.evaluateChallenge calls StringPrep.encode with the profile StringPrep.PROFILE_SASL_STORED https://github.com/wildfly-security/wildfly-elytron/blob/fd74e43caf3e7019... > * StringPrep.PROFILE_SASL_STORED ors PROFILE_SASL_QUERY which ors NORMALIZE_KC https://github.com/wildfly-security/wildfly-elytron/blob/fd74e43caf3e7019... > * StringPrep.encode then normalises using NFKC which replaces U+00A8 with U+0020 U+0308 https://github.com/wildfly-security/wildfly-elytron/blob/fd74e43caf3e7019... > * Active Directory rejects the login > We would be wiling to work on a patch but we need some guidance on the desired solution. A simple solution would be a new profile in StringPrep that doesn't normalize and is used for passwords. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11823) EJB3 subsystem capabilities not recorded in Galleon feature-specs

by Yeray Borges (Jira)

Yeray Borges created WFLY-11823: ----------------------------------- Summary: EJB3 subsystem capabilities not recorded in Galleon feature-specs Key: WFLY-11823 URL: https://issues.jboss.org/browse/WFLY-11823 Project: WildFly Issue Type: Bug Components: Build System Reporter: Yeray Borges Assignee: Yeray Borges These capabilities are registered by EJB3 subsystem but they are not recorded by Galleon feature spec: org.wildfly.ejb3.remote.client-configurator org.wildfly.ejb3 org.wildfly.ejb3.clustered.singleton -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

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 March 2019