April 2015 - jboss-jira - Jboss List Archives

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-424?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-424: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > .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: 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.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-431) CLI should WARN about usage deprecated api

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-431?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-431: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > CLI should WARN about usage deprecated api > ------------------------------------------ > > Key: WFCORE-431 > URL: https://issues.jboss.org/browse/WFCORE-431 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Tomaz Cerar > Assignee: Alexey Loubyansky > Fix For: 1.0.0.CR1 > > > We added support for deprecating resources/attributes/operations/parameters some time ago. > I would be a good thing that we would warn users if they are using deprecated API. > Every resource/attribute/operation/param that is deprecated has extra element "deprecated" in metadata > With sub elements > - "since", which tells in what version it was deprecated > - "reason", text description why it is deprecated. > Reason in most cases also tells what is new replacement. > This should be only displayed in case of interactive shell usage. > Unless there is also some special CLI log file, it could be part of that even for non-interactive usage -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 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 Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-442?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-442: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > 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.15#6346)

9 years, 1 month

1
0
0 / 0

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-459?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-459: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > 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.15#6346)

9 years, 1 month

1
0
0 / 0

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-471?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-471: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > 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.15#6346)

9 years, 1 month

1
0
0 / 0

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-574?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-574: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > 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.15#6346)

9 years, 1 month

1
0
0 / 0

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-579?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-579: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > ProxyMetadataSource does not return JDK8 'default' methods from interfaces > -------------------------------------------------------------------------- > > 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.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-597) Where an ObjectTypeAttributeDefinition is in use respect the ResourceOnly setting on contained types for add operations.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-597?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-597: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Where an ObjectTypeAttributeDefinition is in use respect the ResourceOnly setting on contained types for add operations. > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-597 > URL: https://issues.jboss.org/browse/WFCORE-597 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Labels: affects_elytron > Fix For: 1.0.0.CR1 > > > If an ObjectTypeAttributeDefinition contains an attribute definition that has ResourceOnly set then it should be filtered from the automatically generated description for the add operation. > This may be more related to lists, I currently have: - > ObjectListAttributeDefinition, which contains ObjectTypeAttributeDefinition, which contains SimpleAttributeDefinition > It is this final SimpleAttributeDefinition that has ResourceOnly set but it is still showing up in the operation description for add. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-602) Ability to view an objects index of it's position in a list.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-602?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-602: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Ability to view an objects index of it's position in a list. > ------------------------------------------------------------ > > Key: WFCORE-602 > URL: https://issues.jboss.org/browse/WFCORE-602 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Labels: affects_elytron > Fix For: 1.0.0.CR1 > > > General improvements are being made to the management model for more fine grained manipulation of complex attributes, amongst these changes will be the ability to insert items at a specific position in a list. > This feature request is to ask for the ability to see an items index to identify it's position. > i.e. an end user can call :read-recource and see an items position without needing to count how many items there are in order to identify the position of the next insert. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-598) Make it possible to register a child at a certain position

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-598?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-598: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Make it possible to register a child at a certain position > ---------------------------------------------------------- > > Key: WFCORE-598 > URL: https://issues.jboss.org/browse/WFCORE-598 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 1.0.0.CR1 > > > The BasicResource stores child resources in a LinkedHashMap so it is ordered in the order of the adds. It should be possible to insert a new child somewhere in the middle, rather than just at the end. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2015