March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8487) Autocomplete doesn't work properly in credential-reference.store attribute.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8487?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-8487: ----------------------------------- Priority: Major (was: Critical) > Autocomplete doesn't work properly in credential-reference.store attribute. > --------------------------------------------------------------------------- > > Key: WFLY-8487 > URL: https://issues.jboss.org/browse/WFLY-8487 > Project: WildFly > Issue Type: Bug > Components: Clustering, JCA, JMS, Mail, Security, Web (Undertow) > Affects Versions: 11.0.0.Alpha1 > Reporter: Hynek Švábek > Assignee: Brian Stansberry > Labels: cli, credential-reference, eap71_beta, management-model > > Autocomplete doesn't work properly in credential-reference attribute. > I want to use autocomplete for credential-reference.store but it doesn't work. > *How to reproduce* > {code} > /subsystem=elytron/credential-store=cs1:add(uri="cr-store://test/cs1.jceks", credential-reference={store=<TAB> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1505) Model cannot compile if an item definition is using another item definition that is define after it

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1505?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1505: ------------------------------------- Assignee: Matteo Mortari (was: Edson Tirelli) > Model cannot compile if an item definition is using another item definition that is define after it > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-1505 > URL: https://issues.jboss.org/browse/DROOLS-1505 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Mélanie Gauthier > Assignee: Matteo Mortari > > Let's say you have "Item Definition 1" and "Item Definition 2" in that order in the XML file. > If "Item Definition 1" has one of its component that is of type "Item Definition 2", it won't compile. > If "Item Definition 2" uses "Item Definition 1" then it is fine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1505) Model cannot compile if an item definition is using another item definition that is define after it

by Mélanie Gauthier (JIRA)

Mélanie Gauthier created DROOLS-1505: ---------------------------------------- Summary: Model cannot compile if an item definition is using another item definition that is define after it Key: DROOLS-1505 URL: https://issues.jboss.org/browse/DROOLS-1505 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Mélanie Gauthier Assignee: Edson Tirelli Let's say you have "Item Definition 1" and "Item Definition 2" in that order in the XML file. If "Item Definition 1" has one of its component that is of type "Item Definition 2", it won't compile. If "Item Definition 2" uses "Item Definition 1" then it is fine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8485) Upgrade Narayana to 5.5.6.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-8485?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-8485: -------------------------------- Description: https://issues.jboss.org/projects/JBTM/versions/12334093 https://github.com/jbosstm/narayana/compare/5.5.5.Final...5.5.6.Final > Upgrade Narayana to 5.5.6.Final > ------------------------------- > > Key: WFLY-8485 > URL: https://issues.jboss.org/browse/WFLY-8485 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > https://issues.jboss.org/projects/JBTM/versions/12334093 > https://github.com/jbosstm/narayana/compare/5.5.5.Final...5.5.6.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8486) Upgrade Narayana to 5.5.6.Final

by Tom Jenkinson (JIRA)

Tom Jenkinson created WFLY-8486: ----------------------------------- Summary: Upgrade Narayana to 5.5.6.Final Key: WFLY-8486 URL: https://issues.jboss.org/browse/WFLY-8486 Project: WildFly Issue Type: Component Upgrade Components: Transactions Reporter: Tom Jenkinson Assignee: Tom Jenkinson -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8485) Upgrade Narayana to 5.5.6.Final

by Tom Jenkinson (JIRA)

Tom Jenkinson created WFLY-8485: ----------------------------------- Summary: Upgrade Narayana to 5.5.6.Final Key: WFLY-8485 URL: https://issues.jboss.org/browse/WFLY-8485 Project: WildFly Issue Type: Component Upgrade Components: Transactions Reporter: Tom Jenkinson Assignee: Tom Jenkinson -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1059) RestartParentResourceAdd/RemoveHandler should handle capability registration

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1059?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1059: ------------------------------------------ [~pferraro] is this blocking anything needed for WF 11? If not I want to reschedule it to 4. > RestartParentResourceAdd/RemoveHandler should handle capability registration > ---------------------------------------------------------------------------- > > Key: WFCORE-1059 > URL: https://issues.jboss.org/browse/WFCORE-1059 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.0.CR6 > Reporter: Paul Ferraro > Assignee: Tomaz Cerar > Fix For: 3.0.0.Beta13 > > > RestartParentResourceAddHandler and RestartParentResourceRemoveHandler do not extend the respective AbstractAddStepHandler and AbstractRemoveStepHandler base classes, and thus does not handle capability [un]registration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1960) Get rid of attributes of type LIST of PROPERTY; use OBJECT of STRING

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1960?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1960: ------------------------------------- Fix Version/s: 4.0.0.Alpha1 (was: 3.0.0.Beta13) > Get rid of attributes of type LIST of PROPERTY; use OBJECT of STRING > -------------------------------------------------------------------- > > Key: WFCORE-1960 > URL: https://issues.jboss.org/browse/WFCORE-1960 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Ken Wills > Fix For: 4.0.0.Alpha1 > > Attachments: rrd.txt > > > A read-resource-description output of a standalone-full-ha.xml server (see attached) shows a couple attributes that are of type LIST, value-type PROPERTY. (Just text search for PROPERTY.) We should convert those to OBJECT, value-type STRING. Both represent a resource address. An object of string is equivalent to a LinkedHashMap<String, String>, with ordering based on insertion. So such a description is fine for a path address attribute. > I'd like to get rid of the notion of PROPERTY in our spec definition of how to describe attributes, parameters and value-types (https://docs.jboss.org/author/display/WFLY/Description+of+the+Management+...) so removing the only usage of it will help. > We should still accept PROPERTY as inputs when we can do conversion to the defined type. This is all about tightening up the spec to remove the not-really-necessary PROPERTY concept. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2385) There are two different error messages for adding duplicate record to CS by same command.

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2385?page=com.atlassian.jira.plugi... ] Michal Petrov updated WFCORE-2385: ---------------------------------- Git Pull Request: https://github.com/wildfly-security-incubator/wildfly-core/pull/113 (was: https://github.com/wildfly/wildfly-core/pull/2301) > There are two different error messages for adding duplicate record to CS by same command. > ----------------------------------------------------------------------------------------- > > Key: WFCORE-2385 > URL: https://issues.jboss.org/browse/WFCORE-2385 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Michal Petrov > > There are two different error messages for adding duplicate record to CS by same command. > *How to reproduce* > {code} > /subsystem=elytron/credential-store=cs007:add(uri="cr-store://test/customcredCS007.jceks?create.storage=true", credential-reference={clear-text=pass123}) > {code} > {code} > /subsystem=elytron/credential-store=cs007/alias=alias001:add(secret-value=secret) > {code} > And now we try add there same alias with exactly same name and with name in uppercase > {code} > /subsystem=elytron/credential-store=cs007/alias=alias001:add(secret-value=secret) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0212: Duplicate resource [ > (\"subsystem\" => \"elytron\"), > (\"credential-store\" => \"cs007\"), > (\"alias\" => \"alias001\") > ]", > "rolled-back" => true > } > {code} > {code} > /subsystem=elytron/credential-store=cs007/alias=ALIAS001:add(secret-value=secret) > { > "outcome" => "failed", > "failure-description" => "WFLYELY00913: Credential alias \"alias001\" of credential type \"org.wildfly.security.credential.PasswordCredential\" already exists in the store", > "rolled-back" => true > } > {code} > You can see different error message. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-72) Polarion data cleanup

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-72?page=com.atlassian.jira.plu... ] Sunil kondkar resolved HAWKULARQE-72. ------------------------------------- Resolution: Done > Polarion data cleanup > --------------------- > > Key: HAWKULARQE-72 > URL: https://issues.jboss.org/browse/HAWKULARQE-72 > Project: Hawkular QE > Issue Type: Task > Reporter: Sunil kondkar > Assignee: Sunil kondkar > > Task to able to have polarion reports in place. > Reports: > 1) PQI Metrics: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/wiki/... > 2) Standard Reports: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/wiki/... > 3) Test Run Status by Plan > 4) Test Run Status by Plan and chosen fields > Tasks: > 1) Find and remove duplicates > 2) Each test case has correct fields > * Description > * Level > * Test type and sub type > * Automated or Manual > * Importance (Severity) > 3) Do we need to create a plan in below link? (Like EAP team has release plans created that are used in reports ' Test Run Status by Plan' and 'Test Run Status by Plan and chosen fields' ) > Link: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/plans > 4) Check if manual test cases are with approved status( Approve if needed) > 5) All automated tests (CF-UI test and CFME tests) - need to be changed to Approved from 'Draft' status. > (Need to check if we can have the polarion export job marking it Approved while executed going forward?) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 2017