March 2019 - jboss-jira - Jboss List Archives

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

7 years, 4 months

1
0
0 / 0

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

by Philippe Marschall (Jira)

Philippe Marschall created ELY-1761: --------------------------------------- Summary: 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 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)

7 years, 4 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 jaikiran pai (Jira)

[ https://issues.jboss.org/browse/WFLY-11818?page=com.atlassian.jira.plugin... ] jaikiran pai commented on WFLY-11818: ------------------------------------- Which exact version of Java runtime are you using? > 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)

7 years, 4 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: 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)

7 years, 4 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: 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)

7 years, 4 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: 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)

7 years, 4 months

1
0
0 / 0

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

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3738: -------------------------------------- Summary: 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 Extend DMN DT Analysis to manage Boolean data type -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

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

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3737: -------------------------------------- Summary: 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 Table Consistency in relation with Hit Policy -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

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

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3736: -------------------------------------- Summary: 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 Gaps in relation with Hit Policy -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9459) Outdated doc für ejb client

by Tomasz Adamski (Jira)

[ https://issues.jboss.org/browse/WFLY-9459?page=com.atlassian.jira.plugin.... ] Tomasz Adamski updated WFLY-9459: --------------------------------- Priority: Minor (was: Major) > Outdated doc für ejb client > --------------------------- > > Key: WFLY-9459 > URL: https://issues.jboss.org/browse/WFLY-9459 > Project: WildFly > Issue Type: Bug > Components: Documentation, EJB > Affects Versions: 11.0.0.CR1 > Reporter: Wolfgang Knauf > Assignee: Tomasz Adamski > Priority: Minor > > The WildFly doc contains some pages which should be updated to reflect the change to "WildFly naming client" instead of "EJB client API"/"remote naming project": > [EJB invocations from a remote client using JNDI|https://docs.jboss.org/author/display/WFLY/EJB+invocations+from+a+re...] > [Remote EJB invocations via JNDI - EJB client API or remote-naming project |https://docs.jboss.org/author/display/WFLY/Remote+EJB+invocations+via+JNDI+-+EJB+client+API+or+remote-naming+project] > This should be fixed mainly in the new asciidoc -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 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 March 2019