February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-25) Windows PowerShell scripts in bin

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-25?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-25: ----------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > Windows PowerShell scripts in bin > --------------------------------- > > Key: WFCORE-25 > URL: https://issues.jboss.org/browse/WFCORE-25 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 1.0.0.Beta1 > > > Add .psh scripts that match the functionality of our .sh scripts. Leave the .bat scripts in their current limited-functionality form for people still on XP, but use PowerShell as the recommended Windows scripting language. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-240) We need something similar to StandardConfigsXMLValidationUnitTestCase in Core

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-240?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-240: ------------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > We need something similar to StandardConfigsXMLValidationUnitTestCase in Core > ----------------------------------------------------------------------------- > > Key: WFCORE-240 > URL: https://issues.jboss.org/browse/WFCORE-240 > Project: WildFly Core > Issue Type: Feature Request > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Fix For: 1.0.0.Beta1 > > > One feature of this test is that it validates that schemas are correct according to the schema schema, presently we only find out about errors in schemas when the wildfly testsuite is executed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-137) Add Kerberos tests to domain-management module

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-137?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-137: ------------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > Add Kerberos tests to domain-management module > ---------------------------------------------- > > Key: WFCORE-137 > URL: https://issues.jboss.org/browse/WFCORE-137 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-129) Overlay does not work for subunits in exploded deployments.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-129?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-129: ------------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > Overlay does not work for subunits in exploded deployments. > ----------------------------------------------------------- > > Key: WFCORE-129 > URL: https://issues.jboss.org/browse/WFCORE-129 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha8 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.Beta1 > > > If deployment is exploded and has subdeployments overlay wont work on files contained in said subdeployments. > Reproducers: https://github.com/baranowb/wildfly/tree/WFCORE-83-TESTS -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-107) Update whoami operation to return authentication mechanism where verbose=true

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-107?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-107: ------------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > Update whoami operation to return authentication mechanism where verbose=true > ----------------------------------------------------------------------------- > > Key: WFCORE-107 > URL: https://issues.jboss.org/browse/WFCORE-107 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > The admin console currently contains a "logout" handler that follows a round of HTTP message exchanges to trick the web browser into forgetting the credentials it has cached. > This only makes sense where the browser has cached a credential - if we return the authentication mechanism then the console can make a better decision regarding displaying the logout link or could change the implementation so display a message to the user explaining why logout does not make sense. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-557) Remove usage of jboss-common-core in logging

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-557?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-557: ------------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > Remove usage of jboss-common-core in logging > -------------------------------------------- > > Key: WFCORE-557 > URL: https://issues.jboss.org/browse/WFCORE-557 > Project: WildFly Core > Issue Type: Sub-task > Components: Logging > Affects Versions: 1.0.0.Alpha18 > Reporter: Tomaz Cerar > Assignee: James Perkins > Fix For: 1.0.0.Beta1 > > > we should avoid using jboss-common-core if possible -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-543) Revisit how the model validation happens

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-543?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-543: ------------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > Revisit how the model validation happens > ---------------------------------------- > > Key: WFCORE-543 > URL: https://issues.jboss.org/browse/WFCORE-543 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 1.0.0.Beta1 > > > Currently the ValidateModelStepHandler is triggered by AbstractAddStepHandler. Not all add handlers extend AbstractAddStepHandler. Also, it does not seem to be triggered for writes. > Also if used in a composite along the lines of > {code} > [standalone@localhost:9990 /] batch > [standalone@localhost:9990 / #] /system-property=xxx:add(value=test) > [standalone@localhost:9990 / #] /system-property=xxx:remove > [standalone@localhost:9990 / #] run-batch > {code} > the handler will get triggered at the end for the add. It will fail for the add since there is no such resource. While that is easy to work around by checking for a NoSuchResourceException around the OC.readResource() it seems that what triggers the use of the ValidateModelStepHandler should be more an intrinsic part of the controller which knows what has and has not been added/removed/written to. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-496) add-user.sh - if password contains § it is not possible to log into the webinterface

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-496?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-496: ------------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > add-user.sh - if password contains § it is not possible to log into the webinterface > ------------------------------------------------------------------------------------ > > Key: WFCORE-496 > URL: https://issues.jboss.org/browse/WFCORE-496 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Environment: wheezy, Firefox 34.0.5, Chrome 36.0.1985.125 > Reporter: do ev > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-489) The "access-mechanism" field in the active-operation resources is always undefined

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-489?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-489: ------------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > The "access-mechanism" field in the active-operation resources is always undefined > ---------------------------------------------------------------------------------- > > Key: WFCORE-489 > URL: https://issues.jboss.org/browse/WFCORE-489 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha15 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 1.0.0.Beta1 > > > The "access-mechanism" field in core-service=management/service=active-operations/active-operation=* is always undefined. The code that sets it is using the wrong var: > {code} > ModelNode accessMechanismNode = model.get(ACCESS_MECHANISM); > if (accessMechanism != null) { > accessMechanismNode.set(accessMechanismNode.toString()); > } > {code} > It should be accessMechanism.toString() -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-461) TestSuiteEnvironment should use privileged access to properties

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-461?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-461: ------------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > TestSuiteEnvironment should use privileged access to properties > --------------------------------------------------------------- > > Key: WFCORE-461 > URL: https://issues.jboss.org/browse/WFCORE-461 > Project: WildFly Core > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > Fix For: 1.0.0.Beta1 > > > The current TestSuiteEnvironment uses lots of {{System.getProperty()}} which fail under a security manager. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015