June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-609) Administrator Encouragement

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-609?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-609: --------------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > Administrator Encouragement > --------------------------- > > Key: WFCORE-609 > URL: https://issues.jboss.org/browse/WFCORE-609 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha6 > > > I know the name is not popular so will have a better name ;-) > Essentially some form of centralised repository to hold warnings raised by subsystems as a server boots. > Management operations would be provided to query the current warnings. > As administrators undertake actions to correct a warning it will be dynamically removed by the subsystem that reported it. > This is not about persistent warnings i.e. the subsystem should raise the warning on every boot and stop raising it if it is no longer relevant. > e.g. SSL not enabled, warn every time the server starts until it is enabled. > Warnings will be associated with a severity level and administrative tooling can decide how pro-actively to display the warning, e.g. the console may pop up immediately for a critical warning or use an icon to indicate the presence of a lesser warning. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-597) Where an ObjectTypeAttributeDefinition is in use respect the ResourceOnly setting on contained types for add operations.

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-597?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-597: --------------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > Where an ObjectTypeAttributeDefinition is in use respect the ResourceOnly setting on contained types for add operations. > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-597 > URL: https://issues.jboss.org/browse/WFCORE-597 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Labels: affects_elytron > Fix For: 2.0.0.Alpha6 > > > If an ObjectTypeAttributeDefinition contains an attribute definition that has ResourceOnly set then it should be filtered from the automatically generated description for the add operation. > This may be more related to lists, I currently have: - > ObjectListAttributeDefinition, which contains ObjectTypeAttributeDefinition, which contains SimpleAttributeDefinition > It is this final SimpleAttributeDefinition that has ResourceOnly set but it is still showing up in the operation description for add. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-777) Add ability to use socket binding groups from host subsystems

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-777?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-777: --------------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > Add ability to use socket binding groups from host subsystems > ------------------------------------------------------------- > > Key: WFCORE-777 > URL: https://issues.jboss.org/browse/WFCORE-777 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 2.0.0.Alpha6 > > > Add a single socket-binding group to host model and xml so that HC subsystems can reference those (similar to what happens on a standalone server). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-714) Integrate Elytron with the Remoting subsystem

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-714?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-714: --------------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > Integrate Elytron with the Remoting subsystem > --------------------------------------------- > > Key: WFCORE-714 > URL: https://issues.jboss.org/browse/WFCORE-714 > Project: WildFly Core > Issue Type: Sub-task > Components: Remoting, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha6 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-710) Make ServerOperationResolver handle deployment-overlays similarly to deployments

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-710?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-710: --------------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > Make ServerOperationResolver handle deployment-overlays similarly to deployments > -------------------------------------------------------------------------------- > > Key: WFCORE-710 > URL: https://issues.jboss.org/browse/WFCORE-710 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 2.0.0.Alpha2 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 2.0.0.Alpha6 > > > Currently in domain mode a > {code} > /deployment-overlay=xxx:add(...) > {code} > results in a deployment overlay on ALL servers. > However for deployments > {code} > /deployment=xxx:add(...) > {code} > does not get pushed to the servers. This happens when it is associated with a server group: > {code} > /server-group=zzz/deployment=xxx:add(...) > {code} > Similarly > {code} > /deployment-overlay=xxx:add(...) > {code} > should not get pushed to the servers, until we have a > {code} > /server-group=zzz/deployment=yyy:add(...) > {code} > which picks out the servers we want to have the overlay -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-703) An ObjectTypeAttributeDefinition should recursively handle a resolveModelAttribute call.

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-703?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-703: --------------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > An ObjectTypeAttributeDefinition should recursively handle a resolveModelAttribute call. > ---------------------------------------------------------------------------------------- > > Key: WFCORE-703 > URL: https://issues.jboss.org/browse/WFCORE-703 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Brian Stansberry > Labels: affects_elytron > Fix For: 2.0.0.Alpha6 > > > Expressions will be handled recursively but the default values for the contained AttributeDefinitions should also be recursively handled so that the returned ModelNode is fully populated with both resolved expressions and default values. > Other variants of attributes such as the lists and maps should also be double checked to ensure they are recursive. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-693) Don't require the exclusive management lock to run the "kill" or "destroy" ops on the HC

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-693?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-693: --------------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > Don't require the exclusive management lock to run the "kill" or "destroy" ops on the HC > ---------------------------------------------------------------------------------------- > > Key: WFCORE-693 > URL: https://issues.jboss.org/browse/WFCORE-693 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.0.Alpha6 > > > EDITED: The below isn't quite accurate (ServerShutdownHandler does acquire the exclusive lock) and we need to consider carefully the repurcussions of not doing that. No one should work on this without discussing it with me first. > ServerProcessHandlers.execute is calling context.getServiceRegistry(true) in order to trigger an authorization check. Problem is that also means the exclusive lock needs to be acquired. > There are other ways to handle this. See https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/... for a similar case. > Side issue: the constructor for ServerProcessHandlers should be package-protected. Same with the "serverInventory" field. This isn't a bug, it's just being tidy and locking things down as much as possible. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-688) Remove ServerEnvironment.getModulesDir()

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-688?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-688: --------------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > Remove ServerEnvironment.getModulesDir() > ---------------------------------------- > > Key: WFCORE-688 > URL: https://issues.jboss.org/browse/WFCORE-688 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.0.Alpha6 > > > This method was deprecated in 7.1.0 and the OSGi subsystem is removing the only known use of it in 7.1.2. Remove the method in 7.2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-683) ListModuleRootsHandler and ModuleLocationHandler don't handle PrivilegedActionException properly

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-683?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-683: --------------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > ListModuleRootsHandler and ModuleLocationHandler don't handle PrivilegedActionException properly > ------------------------------------------------------------------------------------------------ > > Key: WFCORE-683 > URL: https://issues.jboss.org/browse/WFCORE-683 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.CR1 > Reporter: Brian Stansberry > Fix For: 2.0.0.Alpha6 > > > The two inner class OSHs in ModuleLoadingResourceDefinition don't deal with exceptions properly. They invoke AccessController.doPrivileged and then deal with any PrivilegedActionException by rethrowing as OperationFailedException. > OperationFailedException represents a client mistake and is handled as such (e.g. isn't logged in the server log.) It shouldn't be thrown here unless the PrivilegedActionException.getCause() value is itself an OFE. Otherwise, the OSHs should throw a RuntimeException. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-779) AbstractAddStepHandler doesn't let AttributeDefinitions record default capability requirements

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-779?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-779: --------------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > AbstractAddStepHandler doesn't let AttributeDefinitions record default capability requirements > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-779 > URL: https://issues.jboss.org/browse/WFCORE-779 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.0.Alpha4 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 2.0.0.Alpha6 > > > AbstractAddStepHandler.recordCapabilitiesAndRequirements(...) has this: > {code} > ModelNode model = resource.getModel(); > for (AttributeDefinition ad : attributes) { > if (model.hasDefined(ad.getName())) { > ad.addCapabilityRequirements(context, model.get(ad.getName())); > } > } > {code} > That 'if' check removes the opportunity for an AD to register a requirement based on the default value of the attribute. > SimpleAttributeDefinition includes logic for doing that, so not giving it a chance to execute is inconsistent. AbstractWriteAttributeHandler also doesn't include any such limitation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 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 June 2015