May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10419) Tests should use snapshots to restore server state rather than manual restoration

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-10419: ------------------------------------- Summary: Tests should use snapshots to restore server state rather than manual restoration Key: WFLY-10419 URL: https://issues.jboss.org/browse/WFLY-10419 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10419) Tests should use snapshots to restore server state rather than manual restoration

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10419?page=com.atlassian.jira.plugin... ] Stuart Douglas reassigned WFLY-10419: ------------------------------------- Assignee: Stuart Douglas > Tests should use snapshots to restore server state rather than manual restoration > --------------------------------------------------------------------------------- > > Key: WFLY-10419 > URL: https://issues.jboss.org/browse/WFLY-10419 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3867) Space char always last char of read system property on Windows

by R Searls (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3867?page=com.atlassian.jira.plugi... ] R Searls commented on WFCORE-3867: ---------------------------------- This jira is related to the other in that the error is seen when running appclient.ps1 testcases from jbossws-cxf > Space char always last char of read system property on Windows > -------------------------------------------------------------- > > Key: WFCORE-3867 > URL: https://issues.jboss.org/browse/WFCORE-3867 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 5.0.0.Beta4 > Reporter: R Searls > Assignee: R Searls > Priority: Minor > > On Windows each system property read has a space char as the last char of string. > This causes failures when the property represents a directory name. Calling > tmp.toPath().toRealPath() in this situation. > ServerEnvironment line, 434 Path resolved = tmp.toPath().toRealPath(); -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1649) RBAC constraint config modifications will fail in a mixed domain if the modified constraint is not present in the legacy slave

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1649?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1649: ------------------------------------- Fix Version/s: 5.0.0.Beta5 (was: 5.0.0.Beta4) > RBAC constraint config modifications will fail in a mixed domain if the modified constraint is not present in the legacy slave > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1649 > URL: https://issues.jboss.org/browse/WFCORE-1649 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Critical > Labels: domain-mode > Fix For: 5.0.0.Beta5 > > > The management model for RBAC constraints is maintained using synthetic resources, with resources only existing for those items (SensitivityClassification and ApplicationClassification) that are registered in the current process. Operations that touch classifications unknown to that process will fail due to missing resource problems. > This is a big problem in the following scenarios: > 1) Mixed domain, where legacy slaves do not know about newly introduced classifications. > 2) Slimming scenarios where slaves are ignoring unrelated parts of the domain wide config and also don't have some extension installed, resulting in classifications registered by those extensions not being present. > A partial workaround to 1) is for the kernel to register transformers for newly introduced classifications (e.g. SERVER_SSL added in EAP 6.4.7 and EAP 7). But: > -- that doesn't help with problem 2) > -- only the kernel can register kernel transformers, so if extensions add new classifications there is no way for them to register the transformer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3867) Space char always last char of read system property on Windows

by R Searls (JIRA)

R Searls created WFCORE-3867: -------------------------------- Summary: Space char always last char of read system property on Windows Key: WFCORE-3867 URL: https://issues.jboss.org/browse/WFCORE-3867 Project: WildFly Core Issue Type: Bug Components: Server Affects Versions: 5.0.0.Beta4 Reporter: R Searls Assignee: R Searls Priority: Minor On Windows each system property read has a space char as the last char of string. This causes failures when the property represents a directory name. Calling tmp.toPath().toRealPath() in this situation. ServerEnvironment line, 434 Path resolved = tmp.toPath().toRealPath(); -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3859) The Elytron subsystem is currently missing any transformation from version 2.0.0 to 1.2.0

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3859?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3859: ------------------------------------- Fix Version/s: 5.0.0.Beta5 (was: 5.0.0.Beta4) > The Elytron subsystem is currently missing any transformation from version 2.0.0 to 1.2.0 > ----------------------------------------------------------------------------------------- > > Key: WFCORE-3859 > URL: https://issues.jboss.org/browse/WFCORE-3859 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 5.0.0.Beta5 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3817) Remove usages of deprecated ServiceListeners

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3817?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3817: ------------------------------------- Fix Version/s: 5.0.0.Beta5 (was: 5.0.0.Beta4) > Remove usages of deprecated ServiceListeners > -------------------------------------------- > > Key: WFCORE-3817 > URL: https://issues.jboss.org/browse/WFCORE-3817 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 5.0.0.Beta5 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3806) Eliminate code that was using transitive MSC dependencies

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3806?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3806: ------------------------------------- Fix Version/s: 5.0.0.Beta5 (was: 5.0.0.Beta4) > Eliminate code that was using transitive MSC dependencies > --------------------------------------------------------- > > Key: WFCORE-3806 > URL: https://issues.jboss.org/browse/WFCORE-3806 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 5.0.0.Beta5 > > > Prior MSC 1.2.8 stability monitors were reporting problems if > some transitive dependency wasn't available. This has changed > since MSC 1.2.8. There is no notion of transitive > dependencies in JBoss MSC anymore. If stability monitor detects > a problem it is always immediate dependency of monitored controller. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10418) Better management of contextual information

by David Lloyd (JIRA)

David Lloyd created WFLY-10418: ---------------------------------- Summary: Better management of contextual information Key: WFLY-10418 URL: https://issues.jboss.org/browse/WFLY-10418 Project: WildFly Issue Type: Enhancement Reporter: David Lloyd We need a better system for tracking context within application server instances. This has many benefits including better operability in embedded modes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2569) [DMN Designer] Marshalling of magnet positions

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2569?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2569: ---------------------------------------- [~roger600] Hi, not sure it helps on it's own! However I see BPMN uses "waypoints" to define connector end-points (and others for presumably orthogonal lines). {code} <bpmndi:BPMNEdge id="_tGgC5Vj0EeiASpIQ4UhanA" bpmnElement="_15A3A674-931B-4285-9F3C-91F2DB5B7EC2" sourceElement="_tGgC4lj0EeiASpIQ4UhanA" targetElement="_tGgC41j0EeiASpIQ4UhanA"> <di:waypoint xsi:type="dc:Point" x="128.0" y="128.0"/> <di:waypoint xsi:type="dc:Point" x="313.0" y="128.0"/> </bpmndi:BPMNEdge> {code} I assume we'd need to also store the "waypoints" and use them when unmarshalling. Do you recall whether the "snap to closest magnet" is "Stunner" or specific to the BPMN marshaller? > [DMN Designer] Marshalling of magnet positions > ---------------------------------------------- > > Key: DROOLS-2569 > URL: https://issues.jboss.org/browse/DROOLS-2569 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Matteo Mortari > > When attaching connectors to different magnets (other than "centre") re-opening a DMN diagram resets connections to the "centre" magnet. IDK if this is an issue with writing magnet positions to the XML or recreating the connections from the XML. > [~tari_manga] could you please liaise with [~roger600] to understand where the issue is? > h2. PR Acceptance test > In DMN Designer, change magnet position in: > - Source node > -- BKM, BKS, Decision, Input > - Target node > -- BKM, BKS, Decision, Annotation -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018