October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3347) add-content operation of deployment resource contains alternative attributes that doesn't exist

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3347?page=com.atlassian.jira.plugi... ] Claudio Miranda updated WFCORE-3347: ------------------------------------ Description: add-content operation contains "content" attribute, {code} /deployment=batch-processing.war:read-operation-description(name=add-content) {code} "content" attribute it is a list of other attributes, they themselves contains the alternatives metadata as {code} "alternatives" => [ "hash", "bytes", "url", "path", "relative-to", "empty" ], {code} But the following attributes doesn't exist: path, relative-to, empty was: {code} /deployment=batch-processing.war:read-operation-description(name=add-content) {code} > add-content operation of deployment resource contains alternative attributes that doesn't exist > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-3347 > URL: https://issues.jboss.org/browse/WFCORE-3347 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Claudio Miranda > Assignee: Brian Stansberry > Priority: Minor > > add-content operation contains "content" attribute, > {code} > /deployment=batch-processing.war:read-operation-description(name=add-content) > {code} > "content" attribute it is a list of other attributes, they themselves contains the alternatives metadata as > {code} > "alternatives" => [ > "hash", > "bytes", > "url", > "path", > "relative-to", > "empty" > ], > {code} > But the following attributes doesn't exist: path, relative-to, empty -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3347) add-content operation of deployment resource contains alternative attributes that doesn't exist

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3347?page=com.atlassian.jira.plugi... ] Claudio Miranda updated WFCORE-3347: ------------------------------------ Description: add-content operation contains "content" attribute, {code} /deployment=*:read-operation-description(name=add-content) {code} "content" attribute it is a list of other attributes, they themselves contains the alternatives metadata as {code} "alternatives" => [ "hash", "bytes", "url", "path", "relative-to", "empty" ], {code} But the following attributes doesn't exist: path, relative-to, empty was: add-content operation contains "content" attribute, {code} /deployment=batch-processing.war:read-operation-description(name=add-content) {code} "content" attribute it is a list of other attributes, they themselves contains the alternatives metadata as {code} "alternatives" => [ "hash", "bytes", "url", "path", "relative-to", "empty" ], {code} But the following attributes doesn't exist: path, relative-to, empty > add-content operation of deployment resource contains alternative attributes that doesn't exist > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-3347 > URL: https://issues.jboss.org/browse/WFCORE-3347 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Claudio Miranda > Assignee: Brian Stansberry > Priority: Minor > > add-content operation contains "content" attribute, > {code} > /deployment=*:read-operation-description(name=add-content) > {code} > "content" attribute it is a list of other attributes, they themselves contains the alternatives metadata as > {code} > "alternatives" => [ > "hash", > "bytes", > "url", > "path", > "relative-to", > "empty" > ], > {code} > But the following attributes doesn't exist: path, relative-to, empty -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3347) add-content operation of deployment resource contains alternative attributes that doesn't exist

by Claudio Miranda (JIRA)

Claudio Miranda created WFCORE-3347: --------------------------------------- Summary: add-content operation of deployment resource contains alternative attributes that doesn't exist Key: WFCORE-3347 URL: https://issues.jboss.org/browse/WFCORE-3347 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Claudio Miranda Assignee: Brian Stansberry Priority: Minor {code} /deployment=batch-processing.war:read-operation-description(name=add-content) {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2197) ability to upload content from secure web server

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2197?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2197: ------------------------------------------ What I'm about to say here would be a separate RFE, but I'll just write it here for now as I think work on WFCORE-2197 would lead to near-simultaneous consideration of: We support "unmanaged" deployments, where instead of the content being uploaded to the content repo and managed by the server, instead the deployment resource indicates a FS location and the deployment is served directly from that location. In theory we could also allow the resource to specify a URL instead of a FS location, plus the necessary config data for elytron authentication, and then the server would pull down that content from the URL as part of deployment. Perhaps this would be useful in cloud-type scenarios as it would eliminate the need to rebuild the cloud image when the deployment is changed. > ability to upload content from secure web server > ------------------------------------------------ > > Key: WFCORE-2197 > URL: https://issues.jboss.org/browse/WFCORE-2197 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Security > Reporter: Ian Kent > > We use the upload-deployment-url operation of wildfly management API to add content to content repository (app war) from remote web server (nexus artifact repository manager). As the nexus web server is secure so the wildfly app server needs to pass credentials to nexus when downloading war to wildfly content repository for deployment. Is there a way to encode the nexus username and password in url parameter or add a additional parameters for username and password. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2584) Domain Mode JMX access through the HostController

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2584?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2584: ------------------------------------- Labels: JMX domain-mode investigation_required (was: JMX investigation_required) > Domain Mode JMX access through the HostController > ------------------------------------------------- > > Key: WFCORE-2584 > URL: https://issues.jboss.org/browse/WFCORE-2584 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, JMX, Remoting > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: JMX, domain-mode, investigation_required > > This task is first to review if this should be considered. > At the moment access to JMX is provided through the remoting connector of each AS instance - this task is to consider if we should actually make it available through the host controller with the host controller acting as a proxy. > The main motivation being to separate management and app traffic. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-332) Allow RestartParentXXXHandlers to handle resources with multiple services

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-332?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFCORE-332. ------------------------------------- Resolution: Won't Do The RestartParentXXXHandlers are there to support what I now see as an anti-pattern -- creating resources that are nothing but config chunks for a parent. Complex attributes on the real resource should be used. So I'd rather put energy into that than into enhancing RestartParent. > Allow RestartParentXXXHandlers to handle resources with multiple services > ------------------------------------------------------------------------- > > Key: WFCORE-332 > URL: https://issues.jboss.org/browse/WFCORE-332 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Richard Achmatowicz > Assignee: Jason Greene > Priority: Minor > > I'd like to use RestartParentWriteAttributeHandler to allow handling of attributes which, when updated, case a restart of only the services installed by their parent resource. These are really useful classes and solve a commonly encountered problem. > However, the resource I want to restart involves four services, and it appears that RestartParentWriteAttriubuteHandler assumes that for every parent key name, there is only a single service registered. > If we had the private methods: > ServiceName[] getParentServiceNames(PathAddress address) > boolean areParentServicesInstalled(ServiceName[] names) > void removeServices(OperationContext context, ServiceNames[] names, ModelNode parentModel) > this could be made to work for more general resources. > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-357) Enhance add-user utility to allow user to select from known groups when assigning groups to a user

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-357?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-357: ------------------------------------ Component/s: Security (was: Domain Management) > Enhance add-user utility to allow user to select from known groups when assigning groups to a user > -------------------------------------------------------------------------------------------------- > > Key: WFCORE-357 > URL: https://issues.jboss.org/browse/WFCORE-357 > Project: WildFly Core > Issue Type: Feature Request > Components: Scripts, Security > Reporter: Darran Lofthouse > > Also ensure add-user utility is talking about groups and not roles. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1391) Check if all elements in elytron-1_0.xsd are parsed correctly in ElytronXmlParser.

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-1391?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev commented on ELY-1391: ------------------------------------ [~honza889] I've checked all elements in elytron-1_0.xsd and compared them to the parser. I've found two issues (see PR). I'm not 100% sure about removing "credential-store" from XSD so please check if that is correct. Another mismatch which I found is that "File-backed realm elements" are present in elytron-1_0.xsd but not in the latest version of the parser which is expected. > Check if all elements in elytron-1_0.xsd are parsed correctly in ElytronXmlParser. > ---------------------------------------------------------------------------------- > > Key: ELY-1391 > URL: https://issues.jboss.org/browse/ELY-1391 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > > Check if all elements in elytron-1_0.xsd are parsed correctly in ElytronXmlParser and vice versa. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3346) Upgrade WildFly Elytron Tool to 1.0.2.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3346?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved JBEAP-13417 to WFCORE-3346: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3346 (was: JBEAP-13417) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) > Upgrade WildFly Elytron Tool to 1.0.2.Final > ------------------------------------------- > > Key: WFCORE-3346 > URL: https://issues.jboss.org/browse/WFCORE-3346 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.5.Final > > > There are no changes to the tool this release however the tool's jar also contains WildFly Elytron so this upgrade is just to bring the two in sync. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3346) Upgrade WildFly Elytron Tool to 1.0.2.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3346?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-3346: ------------------------------------- Fix Version/s: 3.0.5.Final > Upgrade WildFly Elytron Tool to 1.0.2.Final > ------------------------------------------- > > Key: WFCORE-3346 > URL: https://issues.jboss.org/browse/WFCORE-3346 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.5.Final > > > There are no changes to the tool this release however the tool's jar also contains WildFly Elytron so this upgrade is just to bring the two in sync. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 October 2017