August 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-600) Remove minOccurs="1" and maxOccurs="1" from the schema as these are the defaults.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-600?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-600: --------------------------------- Fix Version/s: 1.1.0.Beta9 (was: 1.1.0.Beta8) > Remove minOccurs="1" and maxOccurs="1" from the schema as these are the defaults. > --------------------------------------------------------------------------------- > > Key: ELY-600 > URL: https://issues.jboss.org/browse/ELY-600 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta9 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-609) Unguarded read in ElytronPolicyConfiguration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-609?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-609: --------------------------------- Fix Version/s: 1.1.0.Beta9 (was: 1.1.0.Beta8) > Unguarded read in ElytronPolicyConfiguration > -------------------------------------------- > > Key: ELY-609 > URL: https://issues.jboss.org/browse/ELY-609 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta7 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Labels: static_analysis > Fix For: 1.1.0.Beta9 > > > Access to fields {{uncheckedPermissions}}, {{excludedPermissions}} and {{rolePermissions}} in {{org.wildfly.security.authz.jacc.ElytronPolicyConfiguration}} is holded by lock. However lock is not used in their getter methods. Getters should be also handled by locks to avoid unguarded read of those fields. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-601) Adjust all AuthenticationConfiguration 'use' methods to more closely match the schema

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-601?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-601: --------------------------------- Fix Version/s: 1.1.0.Beta9 (was: 1.1.0.Beta8) > Adjust all AuthenticationConfiguration 'use' methods to more closely match the schema > ------------------------------------------------------------------------------------- > > Key: ELY-601 > URL: https://issues.jboss.org/browse/ELY-601 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta9 > > > Within the schema a lot of these are configured using 'set'*' elements - switch the methods over to set as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-622) Release WildFly Elytron 1.1.0.Beta8

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-622?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-622. ---------------------------------- Resolution: Done > Release WildFly Elytron 1.1.0.Beta8 > ----------------------------------- > > Key: ELY-622 > URL: https://issues.jboss.org/browse/ELY-622 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta8 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1726) CLI support for response attachments

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1726?page=com.atlassian.jira.plugi... ] Brian Stansberry edited comment on WFCORE-1726 at 8/25/16 12:30 PM: -------------------------------------------------------------------- Yes, not returning the uuid is a bug. If we are talking about an attribute, the attribute value in the response's result value must be the uuid. For a custom operation the response's result value must be the uuid. was (Author: brian.stansberry): Yes, not returning the uuid is a bug. If we are talking about an attribute, the attribute value in the normal response must be the uuid. For a custom operation the response's result value must be the uuid. > CLI support for response attachments > ------------------------------------ > > Key: WFCORE-1726 > URL: https://issues.jboss.org/browse/WFCORE-1726 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > CLI doesn't support the streams attached to a response. Incremental deployment support offers today the ability to read the content of a deployment. It would be interesting to operate it from the CLI. Some resource (such as the log file) expose some attributes as stream. > The following operations are returning streams: > /subsystem=logging/log-file=server.log:read-attribute(name=stream) > /subsystem=logging/log-file=server.log:read-resource(include-runtime) > /deployment=toto:read-content(path=index.html) > As we can see, streams can be located in attributes, as operation response, inside a resource. > The CLI offers 2 way to approach the problem: > 1) Extend the Low level operation support with a way to save/display attached streams. This would require some XML configuration and possibly UI workflow to prompt user for the right action. Making from stream to file path would be not ideal and far from being user friendly. The good side is tha tit would work in any case (batch, non batch). The XML configuration can be a bit complex and prompting user is not an ideal workflow. > 2) Define a new high level command that would cope with any operation. > Such command would look like: > attachment save --operation=/subsystem=logging/log-file=server.log:read-attribute(name=stream) --file=/my/local/path/to/file > attachment display --operation=/subsystem=logging/log-file=server.log:read-attribute(name=stream) > - No risk to impact existing scripts. This is a new feature, so people would have to update their scripts to add the command. > - The challenge is located in mapping a Stream to a file name. The user provides the name he wants. Furthermore, in interactive mode, the user can use completion to complete this target file. > - No more prompting, the user knows ahead of time what he wants to do. > - Problem is that batch mode doesn't re-dispatch each step response to each input command. So some logic should be needed to properly handle streams in batch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1726) CLI support for response attachments

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1726?page=com.atlassian.jira.plugi... ] Brian Stansberry edited comment on WFCORE-1726 at 8/25/16 12:29 PM: -------------------------------------------------------------------- Yes, not returning the uuid is a bug. If we are talking about an attribute, the attribute value in the normal response must be the uuid. For a custom operation the response's result value must be the uuid. was (Author: brian.stansberry): Yes, not returning the uuid is a bug. If we are talking about an attribute, the attribute value in the normal response must be the uuid. For a custom operation the response must be the uuid. > CLI support for response attachments > ------------------------------------ > > Key: WFCORE-1726 > URL: https://issues.jboss.org/browse/WFCORE-1726 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > CLI doesn't support the streams attached to a response. Incremental deployment support offers today the ability to read the content of a deployment. It would be interesting to operate it from the CLI. Some resource (such as the log file) expose some attributes as stream. > The following operations are returning streams: > /subsystem=logging/log-file=server.log:read-attribute(name=stream) > /subsystem=logging/log-file=server.log:read-resource(include-runtime) > /deployment=toto:read-content(path=index.html) > As we can see, streams can be located in attributes, as operation response, inside a resource. > The CLI offers 2 way to approach the problem: > 1) Extend the Low level operation support with a way to save/display attached streams. This would require some XML configuration and possibly UI workflow to prompt user for the right action. Making from stream to file path would be not ideal and far from being user friendly. The good side is tha tit would work in any case (batch, non batch). The XML configuration can be a bit complex and prompting user is not an ideal workflow. > 2) Define a new high level command that would cope with any operation. > Such command would look like: > attachment save --operation=/subsystem=logging/log-file=server.log:read-attribute(name=stream) --file=/my/local/path/to/file > attachment display --operation=/subsystem=logging/log-file=server.log:read-attribute(name=stream) > - No risk to impact existing scripts. This is a new feature, so people would have to update their scripts to add the command. > - The challenge is located in mapping a Stream to a file name. The user provides the name he wants. Furthermore, in interactive mode, the user can use completion to complete this target file. > - No more prompting, the user knows ahead of time what he wants to do. > - Problem is that batch mode doesn't re-dispatch each step response to each input command. So some logic should be needed to properly handle streams in batch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1726) CLI support for response attachments

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1726?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1726: ------------------------------------------ Yes, not returning the uuid is a bug. If we are talking about an attribute, the attribute value in the normal response must be the uuid. For a custom operation the response must be the uuid. > CLI support for response attachments > ------------------------------------ > > Key: WFCORE-1726 > URL: https://issues.jboss.org/browse/WFCORE-1726 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > CLI doesn't support the streams attached to a response. Incremental deployment support offers today the ability to read the content of a deployment. It would be interesting to operate it from the CLI. Some resource (such as the log file) expose some attributes as stream. > The following operations are returning streams: > /subsystem=logging/log-file=server.log:read-attribute(name=stream) > /subsystem=logging/log-file=server.log:read-resource(include-runtime) > /deployment=toto:read-content(path=index.html) > As we can see, streams can be located in attributes, as operation response, inside a resource. > The CLI offers 2 way to approach the problem: > 1) Extend the Low level operation support with a way to save/display attached streams. This would require some XML configuration and possibly UI workflow to prompt user for the right action. Making from stream to file path would be not ideal and far from being user friendly. The good side is tha tit would work in any case (batch, non batch). The XML configuration can be a bit complex and prompting user is not an ideal workflow. > 2) Define a new high level command that would cope with any operation. > Such command would look like: > attachment save --operation=/subsystem=logging/log-file=server.log:read-attribute(name=stream) --file=/my/local/path/to/file > attachment display --operation=/subsystem=logging/log-file=server.log:read-attribute(name=stream) > - No risk to impact existing scripts. This is a new feature, so people would have to update their scripts to add the command. > - The challenge is located in mapping a Stream to a file name. The user provides the name he wants. Furthermore, in interactive mode, the user can use completion to complete this target file. > - No more prompting, the user knows ahead of time what he wants to do. > - Problem is that batch mode doesn't re-dispatch each step response to each input command. So some logic should be needed to properly handle streams in batch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6998) problem with lazy relationship and eclipselink 2.6.3 on wildfly 10 final

by Christopher Willems (JIRA)

[ https://issues.jboss.org/browse/WFLY-6998?page=com.atlassian.jira.plugin.... ] Christopher Willems commented on WFLY-6998: ------------------------------------------- log uploaded with stack dumps > problem with lazy relationship and eclipselink 2.6.3 on wildfly 10 final > ------------------------------------------------------------------------ > > Key: WFLY-6998 > URL: https://issues.jboss.org/browse/WFLY-6998 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Christopher Willems > Assignee: Scott Marlow > Attachments: server.zip, server.zip, server.zip > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6998) problem with lazy relationship and eclipselink 2.6.3 on wildfly 10 final

by Christopher Willems (JIRA)

[ https://issues.jboss.org/browse/WFLY-6998?page=com.atlassian.jira.plugin.... ] Christopher Willems updated WFLY-6998: -------------------------------------- Attachment: server.zip > problem with lazy relationship and eclipselink 2.6.3 on wildfly 10 final > ------------------------------------------------------------------------ > > Key: WFLY-6998 > URL: https://issues.jboss.org/browse/WFLY-6998 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Christopher Willems > Assignee: Scott Marlow > Attachments: server.zip, server.zip, server.zip > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-622) Release WildFly Elytron 1.1.0.Beta8

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-622: ------------------------------------ Summary: Release WildFly Elytron 1.1.0.Beta8 Key: ELY-622 URL: https://issues.jboss.org/browse/ELY-622 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta8 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016