April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-429) Incremental redeployment (single file update) over management API

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-429?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-429: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Incremental redeployment (single file update) over management API > ----------------------------------------------------------------- > > Key: WFCORE-429 > URL: https://issues.jboss.org/browse/WFCORE-429 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management > Reporter: Ondrej Zizka > Labels: deploy, deployment, incremental, redeployment > Fix For: 1.0.0.CR1 > > > (Based on JBDS use case - see EAP6-1) > See also https://mojo.redhat.com/docs/DOC-934058 for notes > By incremental redeployment, we mean the situation when something is deployed, and after changes (in IDE e.g.), only that single file (.jsp, .xml, .class) would be re-deployed to the server, *over management API* - which is, you'd give it a stream and a path where it belongs in the deployment, and the operation would accept that file and put it to the right place in VFS, clear caches etc. > Use cases: > Big .war's, mainly on remote > Cloud deployments > Also, you loose sessions etc. > "JSP recompile on file update" - mgmt API operation - added in WildFly 8? > Not expected to work in domain mode. > Stuart said that session persistence is implemented in WFly 8, but not the incremental redeployment. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-424) .jar's on "current runtime classpath"

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-424?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-424: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > .jar's on "current runtime classpath" > ------------------------------------- > > Key: WFCORE-424 > URL: https://issues.jboss.org/browse/WFCORE-424 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Modules > Reporter: Ondrej Zizka > Assignee: David Lloyd > Fix For: 1.0.0.CR1 > > > (Based on JBDS use case - see EAP6-1) > In certain scenarios, JBDS needs to know the classpath. (Compilation of non-maven project, against a remote server, ...(?) ) > The classpath would be: > * for the deployment after deployed > * for a generic deployment if it was deployed right now - what would WildFly use? > * for the deployment before deployed - sounds a bit advanced but technically possible > We (David, Stuart, Jason, Max, Ondra) have discussed this on EAP F2F 2014. > The output was that we don't need exact classpath / list of jars which would probably end up being almost all modules; rather we need the direct deps. As someone said - "just to get rid of the red lines in the IDE". > The non-maven compilation use case is that the user has a server in a directory, and the jars to build against should all be in there. So the IDE should be able to ask WildFly for a list of .jar's to build the application against, and just use that instead of forcing the user to gather them manually. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-403) Evaluate making operation "composite" EntryType.PUBLIC

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-403?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-403: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Evaluate making operation "composite" EntryType.PUBLIC > ------------------------------------------------------ > > Key: WFCORE-403 > URL: https://issues.jboss.org/browse/WFCORE-403 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.CR1 > > > When the composite operation handler is registered, it's marked as EntryType.PRIVATE. This operation really isn't private; any reasonable management client will need to invoke it. > Changing it may have some implications though; we need to evaluate those. The biggest is the operation metadata cannot be complete, because the step parameter elements cannot be fully described. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

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

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-471?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-471: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > 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: 1.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.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-470) support patching through the http mgmt API

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-470?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-470: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > support patching through the http mgmt API > ------------------------------------------ > > Key: WFCORE-470 > URL: https://issues.jboss.org/browse/WFCORE-470 > Project: WildFly Core > Issue Type: Feature Request > Components: Patching > Affects Versions: 1.0.0.Alpha1 > Reporter: Emanuel Muckenhuber > Fix For: 1.0.0.CR1 > > > The patch operation requires an input stream attachment of the patch content, which is not generally supported for all operations of the http API. We probably need to do something similar to the deployment add-content handler. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

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

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-459?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-459: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > 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: 1.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.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-442) AbstractMultiTargetHandler-based handlers do not propagate failures to the top level failure-description

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-442?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-442: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > AbstractMultiTargetHandler-based handlers do not propagate failures to the top level failure-description > -------------------------------------------------------------------------------------------------------- > > Key: WFCORE-442 > URL: https://issues.jboss.org/browse/WFCORE-442 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha13 > Reporter: Brian Stansberry > Assignee: Heiko Braun > Fix For: 1.0.0.CR1 > > > An example is worth a thousand words: > {code} > [standalone@localhost:9990 /] /path=*:query(where={read-only=1}) > { > "outcome" => "failed", > "result" => [ > { > "address" => [("path" => "jboss.server.temp.dir")], > "outcome" => "failed", > "result" => { > "name" => "jboss.server.temp.dir", > "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/tmp", > "read-only" => true, > "relative-to" => undefined > }, > "rolled-back" => true > }, > { > "address" => [("path" => "user.home")], > "outcome" => "failed", > "result" => { > "name" => "user.home", > "path" => "/Users/hbraun", > "read-only" => true, > "relative-to" => undefined > }, > "rolled-back" => true > }, > { > "address" => [("path" => "jboss.server.base.dir")], > "outcome" => "failed", > "result" => { > "name" => "jboss.server.base.dir", > "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone", > "read-only" => true, > "relative-to" => undefined > }, > "rolled-back" => true > }, > { > "address" => [("path" => "java.home")], > "outcome" => "failed", > "result" => { > "name" => "java.home", > "path" => "/Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home/jre", > "read-only" => true, > "relative-to" => undefined > }, > "rolled-back" => true > }, > { > "address" => [("path" => "user.dir")], > "outcome" => "failed", > "result" => { > "name" => "user.dir", > "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT", > "read-only" => true, > "relative-to" => undefined > }, > "rolled-back" => true > }, > { > "address" => [("path" => "jboss.server.data.dir")], > "outcome" => "failed", > "result" => { > "name" => "jboss.server.data.dir", > "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/data", > "read-only" => true, > "relative-to" => undefined > }, > "rolled-back" => true > }, > { > "address" => [("path" => "jboss.home.dir")], > "outcome" => "failed", > "result" => { > "name" => "jboss.home.dir", > "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT", > "read-only" => true, > "relative-to" => undefined > }, > "rolled-back" => true > }, > { > "address" => [("path" => "jboss.server.log.dir")], > "outcome" => "failed", > "result" => { > "name" => "jboss.server.log.dir", > "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/log", > "read-only" => true, > "relative-to" => undefined > }, > "rolled-back" => true > }, > { > "address" => [("path" => "jboss.server.config.dir")], > "outcome" => "failed", > "result" => { > "name" => "jboss.server.config.dir", > "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/configuration", > "read-only" => true, > "relative-to" => undefined > }, > "rolled-back" => true > }, > { > "address" => [("path" => "jboss.controller.temp.dir")], > "outcome" => "failed", > "result" => { > "name" => "jboss.controller.temp.dir", > "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/tmp", > "read-only" => true, > "relative-to" => undefined > }, > "failure-description" => "Illegal argument for attribute 'read-only'. Expected type BOOLEAN", > "rolled-back" => true > } > ], > "rolled-back" => true > } > {code} > One item in the set has a failure description but the overall response does not. > ReadResourceDescriptionHandler handles similar things but has logic for creating an overall failure-description. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-579) ProxyMetadataSource does not return JDK8 'default' methods fro minterfaces

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-579?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-579: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > ProxyMetadataSource does not return JDK8 'default' methods fro minterfaces > -------------------------------------------------------------------------- > > Key: WFCORE-579 > URL: https://issues.jboss.org/browse/WFCORE-579 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha19 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-574) Upgrade jboss-invocation with version that includes fix for WFLY-4316

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-574?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-574: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Upgrade jboss-invocation with version that includes fix for WFLY-4316 > --------------------------------------------------------------------- > > Key: WFCORE-574 > URL: https://issues.jboss.org/browse/WFCORE-574 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Tomaz Cerar > Assignee: David Lloyd > Fix For: 1.0.0.CR1 > > > Upgrade jboss-invocation with version that includes https://github.com/jbossas/jboss-invocation/pull/7 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-557) Remove usage of jboss-common-core in logging

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-557?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-557: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Remove usage of jboss-common-core in logging > -------------------------------------------- > > Key: WFCORE-557 > URL: https://issues.jboss.org/browse/WFCORE-557 > Project: WildFly Core > Issue Type: Sub-task > Components: Logging > Affects Versions: 1.0.0.Alpha18 > Reporter: Tomaz Cerar > Assignee: James Perkins > Fix For: 1.0.0.CR1 > > > we should avoid using jboss-common-core if possible -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 April 2015