December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2785) The HttpDeploymentUploadUnitTestCase needs to be rewritten to use the Apache HttpClient

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2785?page=com.atlassian.jira.plugi... ] James Perkins reassigned WFCORE-2785: ------------------------------------- Assignee: James Perkins > The HttpDeploymentUploadUnitTestCase needs to be rewritten to use the Apache HttpClient > --------------------------------------------------------------------------------------- > > Key: WFCORE-2785 > URL: https://issues.jboss.org/browse/WFCORE-2785 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: James Perkins > Assignee: James Perkins > > The {{org.jboss.as.test.integration.management.http.HttpDeploymentUploadUnitTestCase}} uses the {{java.net.Authenticator.setDefault()}} to set a default authenticator. This can cause issues with tests that run after this test. The authenticator would be used after when the expectation is for the authentication to fail. This test should be converted to use the Apache {{HttpClient}} or at a minimum avoid setting a default authenticator. > It also doesn't look like the test cleans up the deployed content which it should. -Maybe the {{add-content}} request could just be moved to the {{HttpGenericOperationUnitTestCase}} which has some similar actions.- See the {{HttpGenericOperationUnitTestCase}} for an example of using the {{HttpClient}} for a similar test. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-206) Create long running complex environment

by Michael Foley (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-206?page=com.atlassian.jira.pl... ] Michael Foley reassigned HAWKULARQE-206: ---------------------------------------- Assignee: Matt Mahoney (was: Michael Foley) > Create long running complex environment > --------------------------------------- > > Key: HAWKULARQE-206 > URL: https://issues.jboss.org/browse/HAWKULARQE-206 > Project: Hawkular QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Matt Mahoney > Priority: Critical > > Goal of this task is to create environment which would be similar to customer environments. > Proposed steps (will be defined in more details later) > # define typical customer environment (probably secured, hybrid?-EAP running in OS/RHEV..., how many EAPs?, how many applications running, which metrics enabled...) > # dedicate hw resources > # install it > # keep it running as long as possible -> do upgrades the same way like customer would > # set up monitoring for errors > # set up regular reports -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3398) Elytron, wrong capabilities registered

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3398?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFCORE-3398: ---------------------------------- Affects Version/s: 4.0.0.Alpha3 > Elytron, wrong capabilities registered > -------------------------------------- > > Key: WFCORE-3398 > URL: https://issues.jboss.org/browse/WFCORE-3398 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 4.0.0.Alpha3 > Reporter: Martin Choma > Assignee: Ilia Vassilev > > I wen throught resources and > * trust-manager is registered as credential-store besides trust-manager > {code} > "trust-manager" => { > "description" => "A trust manager definition for creating the TrustManager[] as used to create an SSLContext.", > "model-description" => {"*" => { > "description" => "A trust manager definition for creating the TrustManager[] as used to create an SSLContext.", > "capabilities" => [ > { > "name" => "org.wildfly.security.trust-manager", > "dynamic" => true > }, > { > "name" => "org.wildfly.security.credential-store", > "dynamic" => true > } > ], > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-206) Create long running complex environment

by Filip Brychta (JIRA)

Filip Brychta created HAWKULARQE-206: ---------------------------------------- Summary: Create long running complex environment Key: HAWKULARQE-206 URL: https://issues.jboss.org/browse/HAWKULARQE-206 Project: Hawkular QE Issue Type: Task Reporter: Filip Brychta Assignee: Michael Foley Priority: Critical Goal of this task is to create environment which would be similar to customer environments. Proposed steps (will be defined in more details later) # define typical customer environment (probably secured, hybrid?-EAP running in OS/RHEV..., how many EAPs?, how many applications running, which metrics enabled...) # dedicate hw resources # install it # keep it running as long as possible -> do upgrades the same way like customer would # set up monitoring for errors # set up regular reports -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1553) Write documentation for the DMN and FEEL components

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1553?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1553: ---------------------------------- Sprint: 2017 Week 22-23, 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48 (was: 2017 Week 22-23, 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50) > Write documentation for the DMN and FEEL components > --------------------------------------------------- > > Key: DROOLS-1553 > URL: https://issues.jboss.org/browse/DROOLS-1553 > Project: Drools > Issue Type: Task > Components: dmn engine > Affects Versions: 7.0.0.CR3 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.5.0.Final > > > Write the documentation for both FEEL and DMN engines. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2161) Recursive function definitions in context entries are raising compile time errors

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2161?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-2161: ---------------------------------- Sprint: 2017 Week 49-50 > Recursive function definitions in context entries are raising compile time errors > --------------------------------------------------------------------------------- > > Key: DROOLS-2161 > URL: https://issues.jboss.org/browse/DROOLS-2161 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.4.1.Final > Reporter: Edson Tirelli > Assignee: Fedor Gavrilov > Attachments: ContextRecursion.dmn > > > Recursive function definitions in contexts are raising compile time errors but are executing correctly. > See attached model for example. Functions "f" and "h" raise compile time errors. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-205) Create best practices document for polarion on mojo

by Filip Brychta (JIRA)

Filip Brychta created HAWKULARQE-205: ---------------------------------------- Summary: Create best practices document for polarion on mojo Key: HAWKULARQE-205 URL: https://issues.jboss.org/browse/HAWKULARQE-205 Project: Hawkular QE Issue Type: Task Reporter: Filip Brychta Assignee: Michael Foley * create the document * share it with the team -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-204) Create best practices document for writing automation on mojo

by Filip Brychta (JIRA)

Filip Brychta created HAWKULARQE-204: ---------------------------------------- Summary: Create best practices document for writing automation on mojo Key: HAWKULARQE-204 URL: https://issues.jboss.org/browse/HAWKULARQE-204 Project: Hawkular QE Issue Type: Task Reporter: Filip Brychta Assignee: Filip Brychta * create the document * share it with the team -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-203) Intoduce usage of Regression bugzilla keyword

by Filip Brychta (JIRA)

Filip Brychta created HAWKULARQE-203: ---------------------------------------- Summary: Intoduce usage of Regression bugzilla keyword Key: HAWKULARQE-203 URL: https://issues.jboss.org/browse/HAWKULARQE-203 Project: Hawkular QE Issue Type: Task Reporter: Filip Brychta Assignee: Michael Foley Priority: Critical We need to introduce Regression bugzilla keyword to our workflow. This keyword should be used in cases when some already working feature delivered to customers is broken. All issues with this keyword must be fixed before the release -> everything which was working before should be working in newer version too. Following should be done: * introduce the usage to our bugzilla workflow document * notify the whole team (including dev) to start using it * prepare bugzilla query which will list all open issues with this keyword and share it with the team -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3442) CLI can't reload if authentication configuration changed

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3442?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-3442: ----------------------------------------- Description: The context: - Legacy ManagementRealm, no local-auth enabled, only users located properties file. - SASL authentication factory, digest with FooRealm, userName/password in other properties file The http management interface - Reference ManagementRealm and upgrade references SAL factory. >From CLI: 1) User connects using credentials required for FooRealm 2) User disables SASL authentication : /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory,value=undefined 3) User reloads ==> Connection fails. The user should be prompted for ManagementRealm credentials (if the current ones are not valid in the context of this realm). was: The context: - Legacy ManagementRealm, no local-auth enabled, only users located properties file. - SASL authentication factory, digest with FooRealm, userName/password in other properties file The http management interface - Reference ManagementRealm and upgrade references SAL factory. >From CLI: 1) User connects using credentials required for FooRealm 2) User disables SASL authentication : /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory,value=undefined 3) User reloads ==> Connection fails. The user should be prompted for ManagementRealm credentials (if the current ones are not valid in the context of this realm). Furthermore, ConnectionInfo should expose the realm the CLI is connected to. > CLI can't reload if authentication configuration changed > -------------------------------------------------------- > > Key: WFCORE-3442 > URL: https://issues.jboss.org/browse/WFCORE-3442 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > The context: > - Legacy ManagementRealm, no local-auth enabled, only users located properties file. > - SASL authentication factory, digest with FooRealm, userName/password in other properties file > The http management interface > - Reference ManagementRealm and upgrade references SAL factory. > From CLI: > 1) User connects using credentials required for FooRealm > 2) User disables SASL authentication : /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory,value=undefined > 3) User reloads ==> Connection fails. > The user should be prompted for ManagementRealm credentials (if the current ones are not valid in the context of this realm). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 December 2017