May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8630) Tests broken as part of WildFly Core 3.0.0.Beta16

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFLY-8630?page=com.atlassian.jira.plugin.... ] Ken Wills commented on WFLY-8630: --------------------------------- Note: org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase and org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect are moving to wildfly-core, so I'll clone this into WFCORE and update. > Tests broken as part of WildFly Core 3.0.0.Beta16 > ------------------------------------------------- > > Key: WFLY-8630 > URL: https://issues.jboss.org/browse/WFLY-8630 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > > Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated. > org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration > org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase.testClientLoginModule > org.jboss.as.test.integration.ejb.container.interceptor.security.api.SwitchIdentityTestCase.testClientLoginModule > org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect > Failure examples: http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=113878&buildTy... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2456) Obtain password from external source (CMD, EXT) doesn't work on Windows.

by Dmitrii Tikhomirov (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2456?page=com.atlassian.jira.plugi... ] Dmitrii Tikhomirov reassigned WFCORE-2456: ------------------------------------------ Assignee: Jan Kalina (was: Dmitrii Tikhomirov) > Obtain password from external source (CMD, EXT) doesn't work on Windows. > ------------------------------------------------------------------------ > > Key: WFCORE-2456 > URL: https://issues.jboss.org/browse/WFCORE-2456 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Jan Kalina > > Obtain password from external source (CMD, EXT) doesn't work on Windows. > Try to create new CS which obtains password from external source: > {code} > /subsystem=elytron/credential-store=myCredStore:add(uri="cr-store://test/myCredStore.jceks?create=true", credential-reference={clear-text="{CMD}C:\path\to\scrit\pass.bat,VerySecretPassword", type=COMMAND}, relative-to=jboss.server.config.dir) > {code} > pass.bat file contains only this > {code} > echo %1 > {code} > Because of https://issues.jboss.org/browse/JBEAP-9211 you must do this extra step: > Add new alias to CS -> JCEKS file is created > Please try it open directly with pass "VerySecretPassword" -> *it doesn't work* on Windows. > In my opinion there is problem with back slashes in script path. > https://github.com/wildfly/wildfly-core/blob/3.0.0.Alpha22/controller/src... > Because when I add there back slashed to path then it works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-95) Test Case - Topology Fails when Linked to Container

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-95?page=com.atlassian.jira.plu... ] Matt Mahoney updated HAWKULARQE-95: ----------------------------------- BZ Verified: https://bugzilla.redhat.com/show_bug.cgi?id=1447432 > Test Case - Topology Fails when Linked to Container > --------------------------------------------------- > > Key: HAWKULARQE-95 > URL: https://issues.jboss.org/browse/HAWKULARQE-95 > Project: Hawkular QE > Issue Type: Feature Request > Reporter: Matt Mahoney > Assignee: Michael Foley > > Do we have a test case for the following? > " topology view fails once I have a server linked to a container" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2786) Improve the composition operation output

by Filippe Spolti (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2786?page=com.atlassian.jira.plugi... ] Filippe Spolti updated WFCORE-2786: ----------------------------------- Description: When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N. I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example: {code:title=Payload} { "address": [], "json.pretty": 1, "operation": "composite", "steps": [ { "name": "server-state", "operation": "read-attribute" }, { "address": { "deployment": "*" }, "name": "status", "operation": "read-attribute" } ] } {code} {code:title=Response} { "outcome": "success", "result": { "step-1": { "outcome": "success", "result": "running" }, "step-2": { "outcome": "success", "result": [] } } } {code} If you have somethingthat dynamically builds the composite payload, it is very hard to identify the corresponding output to each command in the payload. It will be great if we can add a extra field in the response or change the steps name to its operation name, for example: {code} { "outcome": "success", "result": { "step-1": { "operation-name": "server-state", "outcome": "success", "result": "running" }, "step-2": { "operation-name": "deployment-info", "outcome": "success", "result": [] } } } {code} Or {code} { "outcome": "success", "result": { "server-state": { "outcome": "success", "result": "running" }, "deployment-info": { "outcome": "success", "result": [] } } } {code} was: When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N. I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example: {code:title=Payload} { "address": [], "json.pretty": 1, "operation": "composite", "steps": [ { "name": "server-state", "operation": "read-attribute" }, { "address": { "deployment": "*" }, "name": "status", "operation": "read-attribute" } ] } {code} {code:title=Response} { "outcome": "success", "result": { "step-1": { "outcome": "success", "result": "running" }, "step-2": { "outcome": "success", "result": [] } } } {code} If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload. It will be great if we can add a extra field in the response or change the steps name to its operation name, for example: {code} { "outcome": "success", "result": { "step-1": { "operation-name": "server-state", "outcome": "success", "result": "running" }, "step-2": { "operation-name": "deployment-info", "outcome": "success", "result": [] } } } {code} Or {code} { "outcome": "success", "result": { "server-state": { "outcome": "success", "result": "running" }, "deployment-info": { "outcome": "success", "result": [] } } } {code} > Improve the composition operation output > ---------------------------------------- > > Key: WFCORE-2786 > URL: https://issues.jboss.org/browse/WFCORE-2786 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Filippe Spolti > > When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N. > I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example: > {code:title=Payload} > { > "address": [], > "json.pretty": 1, > "operation": "composite", > "steps": [ > { > "name": "server-state", > "operation": "read-attribute" > }, > { > "address": { > "deployment": "*" > }, > "name": "status", > "operation": "read-attribute" > } > ] > } > {code} > {code:title=Response} > { > "outcome": "success", > "result": { > "step-1": { > "outcome": "success", > "result": "running" > }, > "step-2": { > "outcome": "success", > "result": [] > } > } > } > {code} > If you have somethingthat dynamically builds the composite payload, it is very hard to identify the corresponding output to each command in the payload. > It will be great if we can add a extra field in the response or change the steps name to its operation name, for example: > {code} > { > "outcome": "success", > "result": { > "step-1": { > "operation-name": "server-state", > "outcome": "success", > "result": "running" > }, > "step-2": { > "operation-name": "deployment-info", > "outcome": "success", > "result": [] > } > } > } > {code} > Or > {code} > { > "outcome": "success", > "result": { > "server-state": { > "outcome": "success", > "result": "running" > }, > "deployment-info": { > "outcome": "success", > "result": [] > } > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2786) Improve the composition operation output

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2786?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2786: ------------------------------------- Issue Type: Feature Request (was: Enhancement) I'm changing this to a Feature Request from Enhancement as this will involve behavior that can be explicitly controlled by a user. The semantics of that will need to be analyzed for all relevant scenarios. I don't see this happening for core 3.0 as we're past the point where we are designing new things unless they are required for existing requirements for the release. > Improve the composition operation output > ---------------------------------------- > > Key: WFCORE-2786 > URL: https://issues.jboss.org/browse/WFCORE-2786 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Filippe Spolti > > When you perform a composite operations with many commands the output will be enumerated in steps, like: step-1, step-2, ..., step-N. > I am not sure, but looks like the step-X correspond to the order of the commands sent in the request payload, example: > {code:title=Payload} > { > "address": [], > "json.pretty": 1, > "operation": "composite", > "steps": [ > { > "name": "server-state", > "operation": "read-attribute" > }, > { > "address": { > "deployment": "*" > }, > "name": "status", > "operation": "read-attribute" > } > ] > } > {code} > {code:title=Response} > { > "outcome": "success", > "result": { > "step-1": { > "outcome": "success", > "result": "running" > }, > "step-2": { > "outcome": "success", > "result": [] > } > } > } > {code} > If you have something the dynamically builds the composite payload, it is very hard to identify the output corresponding to each command in the payload. > It will be great if we can add a extra field in the response or change the steps name to its operation name, for example: > {code} > { > "outcome": "success", > "result": { > "step-1": { > "operation-name": "server-state", > "outcome": "success", > "result": "running" > }, > "step-2": { > "operation-name": "deployment-info", > "outcome": "success", > "result": [] > } > } > } > {code} > Or > {code} > { > "outcome": "success", > "result": { > "server-state": { > "outcome": "success", > "result": "running" > }, > "deployment-info": { > "outcome": "success", > "result": [] > } > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1563) Values are always said to be invalid even when the respect the enumeration

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1563?page=com.atlassian.jira.plugi... ] Matteo Mortari edited comment on DROOLS-1563 at 5/16/17 11:30 AM: ------------------------------------------------------------------ [~mgauthier] no worries, thought about mentioning it in case that was saved on some models internally on your side was (Author: tari_manga): [~mgauthier] no worries, though about mentioning it in case that was saved on some models internally on your side > Values are always said to be invalid even when the respect the enumeration > -------------------------------------------------------------------------- > > Key: DROOLS-1563 > URL: https://issues.jboss.org/browse/DROOLS-1563 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Mélanie Gauthier > Assignee: Matteo Mortari > Attachments: RBLoR test.dmn > > > When running the attached file which has one input that is a collection of a complex structure, the constraints on the field is always said to be invalid. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1563) Values are always said to be invalid even when the respect the enumeration

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1563?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-1563: ---------------------------------------- [~mgauthier] no worries, though about mentioning it in case that was saved on some models internally on your side > Values are always said to be invalid even when the respect the enumeration > -------------------------------------------------------------------------- > > Key: DROOLS-1563 > URL: https://issues.jboss.org/browse/DROOLS-1563 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Mélanie Gauthier > Assignee: Matteo Mortari > Attachments: RBLoR test.dmn > > > When running the attached file which has one input that is a collection of a complex structure, the constraints on the field is always said to be invalid. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1565) Implement a KieScanner listener

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1565: ----------------------------------- Summary: Implement a KieScanner listener Key: DROOLS-1565 URL: https://issues.jboss.org/browse/DROOLS-1565 Project: Drools Issue Type: Enhancement Components: core engine Reporter: Mario Fusco Assignee: Matteo Mortari Allow to register a listener on the KieScanner to be notified when a kjar is successfully updated and when the incremental compilation fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1563) Values are always said to be invalid even when the respect the enumeration

by Mélanie Gauthier (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1563?page=com.atlassian.jira.plugi... ] Mélanie Gauthier commented on DROOLS-1563: ------------------------------------------ [~tari_manga] Sorry about the typo! > Values are always said to be invalid even when the respect the enumeration > -------------------------------------------------------------------------- > > Key: DROOLS-1563 > URL: https://issues.jboss.org/browse/DROOLS-1563 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Mélanie Gauthier > Assignee: Matteo Mortari > Attachments: RBLoR test.dmn > > > When running the attached file which has one input that is a collection of a complex structure, the constraints on the field is always said to be invalid. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1564) Change oopath syntax

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1564?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1564: ----------------------------------- Fix Version/s: 7.0.0.Final > Change oopath syntax > -------------------- > > Key: DROOLS-1564 > URL: https://issues.jboss.org/browse/DROOLS-1564 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Blocker > Fix For: 7.0.0.Final > > > It is required to change the oopath syntax to make it closer to xpath one. This means that constraints will have to be put between square brackets instead of curly ones and inline cast should be expressed out of constraints. In other words the following oopath: > {code} > /list{#SubClass, prop == 0} > {code} > should become: > {code} > /list#SubClass[prop == 0] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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