May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1578) Add link in docs to decision table reference

by Russell Morrisey (JIRA)

Russell Morrisey created DROOLS-1578: ---------------------------------------- Summary: Add link in docs to decision table reference Key: DROOLS-1578 URL: https://issues.jboss.org/browse/DROOLS-1578 Project: Drools Issue Type: Enhancement Components: docs Reporter: Russell Morrisey Assignee: Mario Fusco 6.5.3. How Decision Tables Work "Referring to row 14 (the row immediately after RuleTable), the keywords CONDITION and ACTION indicate that the data in the columns below are for either the LHS or the RHS parts of a rule. There are other attributes on the rule which can also be optionally set this way." What other attributes? Link me to an EBNF, a javadoc, or another part of the guide that has a complete reference. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8836) Allow build to clean tests artefacts to reduce space usage on CI

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-8836?page=com.atlassian.jira.plugin.... ] ehsavoie Hugonnet moved JBEAP-11123 to WFLY-8836: ------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8836 (was: JBEAP-11123) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.DR18) > Allow build to clean tests artefacts to reduce space usage on CI > ---------------------------------------------------------------- > > Key: WFLY-8836 > URL: https://issues.jboss.org/browse/WFLY-8836 > Project: WildFly > Issue Type: Bug > Components: Build System > Affects Versions: 11.0.0.Alpha1 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > Currently a lot of integration tests will leave one or more server used for the tests behind. This will take a lot of space on the disk for no value. We should remove them (while keeping the logs as those might provide meaningful informations in the case of failure). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1185) Only the last mechanism selector is used in Elytron client configuration

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1185?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1185: --------------------------------- Already resolved by https://github.com/wildfly-security/wildfly-elytron/pull/827 (ELY-1184), will be only test-covered. > Only the last mechanism selector is used in Elytron client configuration > ------------------------------------------------------------------------ > > Key: ELY-1185 > URL: https://issues.jboss.org/browse/ELY-1185 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta42 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > > When Elytron client configuration file includes {{sasl-mechanism-selector}} with string which contains more mechanisms then only the last mentioned mechanism is used. In correct behavior it should use all given mechanisms in given order, see [1]. > In case when the last given mechanism is supported by server then it tries to authenticate, otherwise no mechanism is used to attempt to authenticate. > For example, following element for selector can be used in Elytron client configuration file: > {code} > <sasl-mechanism-selector selector="PLAIN DIGEST-MD5 ANONYMOUS JBOSS-LOCAL-USER"/> > {code} > When only {{DIGEST-MD5}} is supported by server then it works only if {{DIGEST-MD5}} is the last mechanism in selector string. > [1] https://issues.jboss.org/browse/EAP7-567?focusedCommentId=13408238&page=c... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1577) Support FIFO queue for agenda group focus

by Russell Morrisey (JIRA)

Russell Morrisey created DROOLS-1577: ---------------------------------------- Summary: Support FIFO queue for agenda group focus Key: DROOLS-1577 URL: https://issues.jboss.org/browse/DROOLS-1577 Project: Drools Issue Type: Feature Request Affects Versions: 6.5.0.Final Reporter: Russell Morrisey Assignee: Edson Tirelli When setting up the ordering of agenda groups, the framework should support adding them in the order they are supposed to be executed. Ex: agenda.getAgendaGroup( "calculation" ).setQueue(); agenda.getAgendaGroup( "report" ).setQueue(); Or, even better: agenda.addAgendaGroupsToQueue("calculation", "report"); And: agenda.addAgendaGroupsToQueue(agenda.getAgendaGroup( "calculation" ), agenda.getAgendaGroup( "report" )) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7351) JAX-RS Http Client does not support SNI even though underlying Apache HttpClient version supports it

by R Searls (JIRA)

[ https://issues.jboss.org/browse/WFLY-7351?page=com.atlassian.jira.plugin.... ] R Searls commented on WFLY-7351: -------------------------------- I tested againts 3.1.2.Final and it works there as well. > JAX-RS Http Client does not support SNI even though underlying Apache HttpClient version supports it > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-7351 > URL: https://issues.jboss.org/browse/WFLY-7351 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 10.1.0.Final > Environment: N/A > Reporter: Edvin Syse > Assignee: Alessio Soldano > Labels: httpclient, https, jax-rs > Attachments: httpclient-sni-bug.zip > > > When creating a JAX-RS client using ClientBuilder.newClient() and accessing an SSL resource configured with SNI, the request fails. > When the request is made you get the default certificate for the ip as it is configured on the web server instead of the certificate corresponding to the host name you entered. > Attached is a simple Maven project with a rest endpoint that will make a request to https://www.syse.no/, which is a host configured with SNI. If you access this host with a client that is not SNI capable, you will get the default certificate instead of the one corresponding to www.syse.no. (That cert is actually expired, so that is the underlying cause reported by the http client in this case. In other cases you will most probably just get a name mismatch type of error). > This effectively prevents the Http client from being used reliably against a rapidly growing number of SSL enabled sites, as SNI is the new standard "everywhere" SSL is configured these days. > The underlying Apache HttpClient version does indeed support SNI. I have tested the version of Apache HttpClient that is bundled with Wildfly 10.1 and it works correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7351) JAX-RS Http Client does not support SNI even though underlying Apache HttpClient version supports it

by R Searls (JIRA)

[ https://issues.jboss.org/browse/WFLY-7351?page=com.atlassian.jira.plugin.... ] R Searls closed WFLY-7351. -------------------------- Resolution: Out of Date > JAX-RS Http Client does not support SNI even though underlying Apache HttpClient version supports it > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-7351 > URL: https://issues.jboss.org/browse/WFLY-7351 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 10.1.0.Final > Environment: N/A > Reporter: Edvin Syse > Assignee: Alessio Soldano > Labels: httpclient, https, jax-rs > Attachments: httpclient-sni-bug.zip > > > When creating a JAX-RS client using ClientBuilder.newClient() and accessing an SSL resource configured with SNI, the request fails. > When the request is made you get the default certificate for the ip as it is configured on the web server instead of the certificate corresponding to the host name you entered. > Attached is a simple Maven project with a rest endpoint that will make a request to https://www.syse.no/, which is a host configured with SNI. If you access this host with a client that is not SNI capable, you will get the default certificate instead of the one corresponding to www.syse.no. (That cert is actually expired, so that is the underlying cause reported by the http client in this case. In other cases you will most probably just get a name mismatch type of error). > This effectively prevents the Http client from being used reliably against a rapidly growing number of SSL enabled sites, as SNI is the new standard "everywhere" SSL is configured these days. > The underlying Apache HttpClient version does indeed support SNI. I have tested the version of Apache HttpClient that is bundled with Wildfly 10.1 and it works correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8835) Create test case for Elytron custom-credential-security-factory resource

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8835?page=com.atlassian.jira.plugin.... ] Hynek Švábek reassigned WFLY-8835: ---------------------------------- Assignee: Hynek Švábek > Create test case for Elytron custom-credential-security-factory resource > ------------------------------------------------------------------------ > > Key: WFLY-8835 > URL: https://issues.jboss.org/browse/WFLY-8835 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Hynek Švábek > Assignee: Hynek Švábek > > Create test case for custom-credential-security-factory resource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8834) Create test cases for Elytron custom-* resources

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8834?page=com.atlassian.jira.plugin.... ] Hynek Švábek reassigned WFLY-8834: ---------------------------------- Assignee: Hynek Švábek > Create test cases for Elytron custom-* resources > ------------------------------------------------ > > Key: WFLY-8834 > URL: https://issues.jboss.org/browse/WFLY-8834 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Hynek Švábek > Assignee: Hynek Švábek > > Create test cases for following Elytron custom-* resources: > * custom-modifiable-realm > * custom-permission-mapper > * custom-principal-decoder > * custom-principal-transformer > * custom-realm > * custom-realm-mapper > * custom-role-decoder > * custom-role-mapper -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8835) Create test case for Elytron custom-credential-security-factory resource

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-8835: ---------------------------------- Summary: Create test case for Elytron custom-credential-security-factory resource Key: WFLY-8835 URL: https://issues.jboss.org/browse/WFLY-8835 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Hynek Švábek Create test case for custom-credential-security-factory resource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8834) Create test cases for Elytron custom-* resources

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-8834: ---------------------------------- Summary: Create test cases for Elytron custom-* resources Key: WFLY-8834 URL: https://issues.jboss.org/browse/WFLY-8834 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Hynek Švábek Create test cases for following Elytron custom-* resources: * custom-modifiable-realm * custom-permission-mapper * custom-principal-decoder * custom-principal-transformer * custom-realm * custom-realm-mapper * custom-role-decoder * custom-role-mapper -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 May 2017