August 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-60) Capabilities and requirements in a managed process

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-60?page=com.atlassian.jira.plugin.... ] James Perkins updated WFCORE-60: -------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.Beta5) > Capabilities and requirements in a managed process > -------------------------------------------------- > > Key: WFCORE-60 > URL: https://issues.jboss.org/browse/WFCORE-60 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.0.CR1 > > > Implement the aspects discussed under the "Runtime" section of https://community.jboss.org/docs/DOC-52712 > Add an API to the OperationContext for handlers to publish capabilities and for other handlers to register a requirement for those capabilities and to access the API object associated with the capability. > The registry of capabilities and requirements should be maintained with a semantic equivalent to the resource tree. The registry is copied-on-write, making the copy invisible to concurrently executing operations, and then the copy is published on commit of the operation that modified it. If the operation does not commit, the copy is discarded, so handlers have no need to revert changes they make to the registry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-54) Add Keycloak authentication/authorization to http management endpoint

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-54?page=com.atlassian.jira.plugin.... ] James Perkins updated WFCORE-54: -------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.Beta5) > Add Keycloak authentication/authorization to http management endpoint > --------------------------------------------------------------------- > > Key: WFCORE-54 > URL: https://issues.jboss.org/browse/WFCORE-54 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 1.0.0.Alpha4 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 2.0.0.CR1 > > > This is here to track the core changes needed for WFLY-3591. See that jira for details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-603) Simplify working with complex attributes

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-603?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-603: --------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.Beta5) > Simplify working with complex attributes > ---------------------------------------- > > Key: WFCORE-603 > URL: https://issues.jboss.org/browse/WFCORE-603 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 2.0.0.CR1 > > > This is umbrella issue for all complex attributes related enhancements and simplifications. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-471) pre/post cli-scripts for AS patching feature

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-471?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-471: --------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.Beta5) > pre/post cli-scripts for AS patching feature > -------------------------------------------- > > Key: WFCORE-471 > URL: https://issues.jboss.org/browse/WFCORE-471 > Project: WildFly Core > Issue Type: Feature Request > Components: Patching , Scripts > Reporter: Nicklas Karlsson > Assignee: Alexey Loubyansky > Fix For: 2.0.0.CR1 > > > It would be handy to be able to attach pre/post CLI scripts to be applied for an AS patch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-459) Account for attribute groups in CLI behavior

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-459?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-459: --------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.Beta5) > Account for attribute groups in CLI behavior > -------------------------------------------- > > Key: WFCORE-459 > URL: https://issues.jboss.org/browse/WFCORE-459 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Brian Stansberry > Assignee: Alexey Loubyansky > Fix For: 2.0.0.CR1 > > > See http://lists.jboss.org/pipermail/wildfly-dev/2014-December/003414.html > This JIRA is for reflecting the attribute group notion in CLI behavior. > I think this is just reflecting it in the output of the "ls -l" command, although there may be other places I'm not thinking of. For "ls -l" simplest is just to add a GROUP column to the right, and then sort the attributes by group and then by name, but perhaps something else is better. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-396) Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-396?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-396: --------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.Beta5) > Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users > --------------------------------------------------------------------------------------------- > > Key: WFCORE-396 > URL: https://issues.jboss.org/browse/WFCORE-396 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Ken Wills > Fix For: 2.0.0.CR1 > > > Ops registered on a domain server without the RUNTIME_ONLY flag are hidden from users (e.g. in read-operation-names results etc) in order to not delude users into thinking they can do something like :write-attribute directly on a server (instead of modifying host or domain config elements.) > But shouldn't a READ_ONLY flag be sufficient as well? An op that only reads config should be valid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-384) Server does wrongly reference a list of socket binding groups

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-384?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-384: --------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.Beta5) > Server does wrongly reference a list of socket binding groups > ------------------------------------------------------------- > > Key: WFCORE-384 > URL: https://issues.jboss.org/browse/WFCORE-384 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Ken Wills > Fix For: 2.0.0.CR1 > > > hbraun: i see that a server (host=foo/server=bar) can have a list of socket-binding-groups > [10:59am] hbraun: shouldn't that be a a single socket binding instead? > [11:00am] emuckenhuber: oh... yeah > [11:00am] hbraun: maybe it's just the description that's wrong > [11:00am] emuckenhuber: that sounds similar to the jvm thing we had -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-365) inconsistent usage of min/max-occurs in model description

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-365?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-365: --------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.Beta5) > inconsistent usage of min/max-occurs in model description > --------------------------------------------------------- > > Key: WFCORE-365 > URL: https://issues.jboss.org/browse/WFCORE-365 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Emanuel Muckenhuber > Assignee: Brian Stansberry > Fix For: 2.0.0.CR1 > > Attachments: patch.txt > > > The usages of min/max-occurs in the model description are not consistent - e.g. missing in ResourceDescription, mostly wrong when used in the descriptionProvider or outdated examples in the documentation. > I'll attach a simple patch which should actually fix that issue in line with the documentation [1] (incl. recursive usage) and the usage of the CLI (ls -l). However there might be more to it. > [1] https://docs.jboss.org/author/display/AS71/Description+of+the+Management+... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-363) ManagementResourceRegistration.getOverrideModel never returns null

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-363?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-363: --------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.Beta5) > ManagementResourceRegistration.getOverrideModel never returns null > ------------------------------------------------------------------ > > Key: WFCORE-363 > URL: https://issues.jboss.org/browse/WFCORE-363 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 2.0.0.CR1 > > > ManagementResourceRegistration.getOverrideModel ends up returning the wildcard registration if there is no override registration. This isn't correct. > The fix isn't trivial because fixing it results in nasty failures in the smoke tests. From looking at the uses of this method (which all involve a null check) I assume there are some bugs in the code that calls this method that get exposed once it does what it should. > This bug is the cause of the initial failure of my WFLY-2880 fix. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-313) DefaultOperationDescriptionProvider uses incorrect call to create reply parameter description

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-313?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-313: --------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.Beta5) > DefaultOperationDescriptionProvider uses incorrect call to create reply parameter description > --------------------------------------------------------------------------------------------- > > Key: WFCORE-313 > URL: https://issues.jboss.org/browse/WFCORE-313 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 2.0.0.CR1 > > > When creating reply descriptions, DefaultOperationDescriptionProvider calls attributeDescriptionResolver.getOperationParameterDescription instead of attributeDescriptionResolver.getOperationReplyValueTypeDescription. > A fix needs to not break compatibility for existing users of the incorrect behavior; i.e. call the correct method in a try block, catch any MissingResourceException, and if caught call the incorrect method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2015