September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1693) Upgrade to JBoss Remoting 5.0.0.Beta4

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1693?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1693: ------------------------------------- Fix Version/s: 3.0.0.Alpha7 (was: 3.0.0.Alpha6) > Upgrade to JBoss Remoting 5.0.0.Beta4 > ------------------------------------- > > Key: WFCORE-1693 > URL: https://issues.jboss.org/browse/WFCORE-1693 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha7 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1692) Upgrade to JBoss Modules 1.6.0.Beta1

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1692?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1692: ------------------------------------- Fix Version/s: 3.0.0.Alpha7 (was: 3.0.0.Alpha6) > Upgrade to JBoss Modules 1.6.0.Beta1 > ------------------------------------ > > Key: WFCORE-1692 > URL: https://issues.jboss.org/browse/WFCORE-1692 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Modules > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha7 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1691) Upgrade to Remoting JMX 3.0.0.Alpha1

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1691?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1691: ------------------------------------- Fix Version/s: 3.0.0.Alpha7 (was: 3.0.0.Alpha6) > Upgrade to Remoting JMX 3.0.0.Alpha1 > ------------------------------------ > > Key: WFCORE-1691 > URL: https://issues.jboss.org/browse/WFCORE-1691 > Project: WildFly Core > Issue Type: Component Upgrade > Components: JMX > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha7 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1602) Elytron integration with JMX

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1602?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1602: ------------------------------------- Fix Version/s: 3.0.0.Alpha7 (was: 3.0.0.Alpha6) > Elytron integration with JMX > ---------------------------- > > Key: WFCORE-1602 > URL: https://issues.jboss.org/browse/WFCORE-1602 > Project: WildFly Core > Issue Type: Feature Request > Components: JMX > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha7 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1600) Update the legacy security realms to add factory methods to obtain SaslAuthenticationFactory and HttpAuthenticationFactory instances.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1600?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1600: ------------------------------------- Fix Version/s: 3.0.0.Alpha7 (was: 3.0.0.Alpha6) > Update the legacy security realms to add factory methods to obtain SaslAuthenticationFactory and HttpAuthenticationFactory instances. > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1600 > URL: https://issues.jboss.org/browse/WFCORE-1600 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha7 > > > These are for use when security realms are directly referenced, although Elytron types these should not be advertised as capabilities as these are for specific backwards compatibility requirements and not to increase their use as Elytron capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1701) In-VM Identity Representation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1701?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1701: ------------------------------------- Fix Version/s: 3.0.0.Alpha7 (was: 3.0.0.Alpha6) > In-VM Identity Representation > ----------------------------- > > Key: WFCORE-1701 > URL: https://issues.jboss.org/browse/WFCORE-1701 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha7 > > > If Elytron has no current SecurityIdentity then an anonymous identity is used. The issue however is that this anonymous identity could be because the current user does not have access to be inflowed to the SecurityDomain being used for management or it could be because it is an in-vm call and no identity is established. > We need a solution to safely represent an in-vm call and differentiate it from a user with no appropriate identity, -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1694) Upgrade to WildFly Client Config 1.0.0.Beta1

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1694?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1694: ------------------------------------- Fix Version/s: 3.0.0.Alpha7 (was: 3.0.0.Alpha6) > Upgrade to WildFly Client Config 1.0.0.Beta1 > -------------------------------------------- > > Key: WFCORE-1694 > URL: https://issues.jboss.org/browse/WFCORE-1694 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha7 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1733) SynchServerOperationHandler doesn't check ops for REQUIRE_RESTART properly

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1733?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1733: ------------------------------------- Fix Version/s: 3.0.0.Alpha7 (was: 3.0.0.Alpha6) > SynchServerOperationHandler doesn't check ops for REQUIRE_RESTART properly > -------------------------------------------------------------------------- > > Key: WFCORE-1733 > URL: https://issues.jboss.org/browse/WFCORE-1733 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 3.0.0.Alpha7 > > > Currently, SyncServerStateOperationHandler makes a simple check to determine if the result of an op should put a server into restart-required. This should be fixed to check the AttributeDefinition for the target of a write-attribute for restart-required, and the OperationDefinition of all other ops. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1741) read-content operation does not return the uuid of the stream as the operation result

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1741?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1741: ------------------------------------- Fix Version/s: 3.0.0.Alpha7 (was: 3.0.0.Alpha6) > read-content operation does not return the uuid of the stream as the operation result > ------------------------------------------------------------------------------------- > > Key: WFCORE-1741 > URL: https://issues.jboss.org/browse/WFCORE-1741 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Fix For: 3.0.0.Alpha7 > > > See the tail end of the discussion on WFCORE-1726. > The rules around streams in responses are: > 1) If the thing providing the stream is an attribute, the attribute value set by the read OperationStepHandler must be the uuid of the stream. > 2) If the thing providing the stream is a custom operation like :read-content, the result value in the response must be the uuid of the stream or a complex result object one of whose fields is the uuid of the stream. > Metadata about streams is propagated to the client using a response-header. But since a particular request can result in more than one attached stream, the normal non-response-header part of the result for a step must provide the uuid of the stream set by that step. This allows the client to correlate the various streams with the steps that provided them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1682) Missleading tab completion for edit-batch-line command

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1682?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1682: ------------------------------------------ Did the revert resolve this? > Missleading tab completion for edit-batch-line command > ------------------------------------------------------ > > Key: WFCORE-1682 > URL: https://issues.jboss.org/browse/WFCORE-1682 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Petr Kremensky > Assignee: Jean-Francois Denise > > Tab completion for edit-batch-list command suggest to use --line-number as a command option, but that is not how the command works. > *command usage* > {noformat} > [standalone@localhost:9990 /] batch > [standalone@localhost:9990 / #] :read-resource > [standalone@localhost:9990 / #] list-batch > #1 /:read-resource > [standalone@localhost:9990 / #] edit-batch-line 1 :read-attribute(name=launch-type) > #1 :read-attribute(name=launch-type) > [standalone@localhost:9990 / #] list-batch > #1 :read-attribute(name=launch-type) > {noformat} > *actual* > {noformat} > [standalone@localhost:9990 / #] edit-batch-line <TAB> > [standalone@localhost:9990 / #] edit-batch-line --<TAB> > --help --line-number > [standalone@localhost:9990 / #] edit-batch-line --line-number=1 :read-attribute(name=launch-type) > Failed to parse line number '--line-number=1': For input string: "--line-number=1" > {noformat} > {{--line-number}} shouldn't be offered by tab completion for the command. > Misleading tab completion ends up with syntax error. > *expected* > {noformat} > [standalone@localhost:9990 / #] edit-batch-line <TAB> > --help > {noformat} > The issue is a regression against EAP 7.0.0 release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2016