February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-130) KeyStoreBackedSecurityRealm Testing

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/ELY-130?page=com.atlassian.jira.plugin.sy... ] Stefan Guilhen reassigned ELY-130: ---------------------------------- Assignee: Stefan Guilhen (was: Darran Lofthouse) > KeyStoreBackedSecurityRealm Testing > ----------------------------------- > > Key: ELY-130 > URL: https://issues.jboss.org/browse/ELY-130 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Darran Lofthouse > Assignee: Stefan Guilhen > Fix For: 1.0.0.Alpha1 > > > For the early subsystem integration work this realm is an ideal option to get in - however before that add some testing so we can verify it will behave the way we need it to. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-569) Clean the DiscoveryIOption API

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-569?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet updated WFCORE-569: ------------------------------------- Summary: Clean the DiscoveryIOption API (was: CLean the DiscoveryIOption API) > Clean the DiscoveryIOption API > ------------------------------ > > Key: WFCORE-569 > URL: https://issues.jboss.org/browse/WFCORE-569 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 1.0.0.Alpha19 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > DiscoveryOption discover should return a list of connection parameters to a DC instead of only one value set into the DiscoveryOption. > Add a ConnectionParameter class with protocol, host and post and returns a list of those when discovering so that we may have multiple options ofr S3 for example. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-569) CLean the DiscoveryIOption API

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-569: ---------------------------------------- Summary: CLean the DiscoveryIOption API Key: WFCORE-569 URL: https://issues.jboss.org/browse/WFCORE-569 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Affects Versions: 1.0.0.Alpha19 Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet DiscoveryOption discover should return a list of connection parameters to a DC instead of only one value set into the DiscoveryOption. Add a ConnectionParameter class with protocol, host and post and returns a list of those when discovering so that we may have multiple options ofr S3 for example. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-565) StaticDiscoveryResourceDefinition allows undefined values for its attributes

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-565?page=com.atlassian.jira.plugin... ] Alexey Loubyansky reassigned WFCORE-565: ---------------------------------------- Assignee: Alexey Loubyansky > StaticDiscoveryResourceDefinition allows undefined values for its attributes > ---------------------------------------------------------------------------- > > Key: WFCORE-565 > URL: https://issues.jboss.org/browse/WFCORE-565 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Alexey Loubyansky > > StaticDiscoveryResourceDefinition reuses the AttributeDefinitions from RemoteDomainControllerAddHandler, but those ADs allow undefined. That's appropriate for that OSH, but not for the StaticDiscoveryResourceDefinition ADs. > Also, the RemoteDomainControllerAddHandler AD's could use some clarification and validation as well, e.g. use setRequires(...) on the builder such that each of protocol, host, port requires the other two. So none are required, but if any is set all 3 must be. > The StaticDiscovery constructor should validate inputs with assert statements and javadoc its parameters, include whether null is allowed. (A null protocol or host will result in an IAE in discover(), so the current code does not support null.) > The DiscoveryOption interface should document whether the 3 "get" methods can return null. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-411: ------------------------------------ Comment: was deleted (was: Cross post. :)) > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-411: ----------------------------------------- That's true if there's no script involved to run the package manager. And the authors of any such script can perhaps be really careful too. I don't mean to turn this into a package manager design thread though. :) > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-411: ----------------------------------------- Cross post. :) > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-411: ------------------------------------ Comment: was deleted (was: That's true if there's no script involved to run the package manager. And the authors of any such script can perhaps be really careful too. I don't mean to turn this into a package manager design thread though. :)) > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFCORE-411: ------------------------------------ I guess that doesn't answer the problem, but I envisioned that the launchers for the patch tool would be single-line affairs. Though it wouldn't hurt to add a line to the top saying: {code} # Line numbers must be preserved {code} or some such. > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFCORE-411: ------------------------------------ Separate package manager can cope by anticipating the situation and pre-initializing all classes it will need for the upgrade operation, so that if its JAR goes away, it can still finish the operation. > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- 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