December 2014 - jboss-jira - Jboss List Archives

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-431?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3622 to WFCORE-431: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-431 (was: WFLY-3622) Component/s: CLI (was: CLI) Fix Version/s: 1.0.0.Beta1 (was: 9.0.0.Beta1) > 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.Beta1 > > > 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.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-432) CLI: Embedded Arrays need to be updatable easily

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-432?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1180 to WFCORE-432: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-432 (was: WFLY-1180) Component/s: CLI (was: CLI) > CLI: Embedded Arrays need to be updatable easily > ------------------------------------------------ > > Key: WFCORE-432 > URL: https://issues.jboss.org/browse/WFCORE-432 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jim Tyrrell > Assignee: Alexey Loubyansky > Labels: eap6-ux > > In the EAP 6 pilot we were presented a long string to create a Database Security Realm, it appears there is no way to update a single value. For example being able to change the string of the SQL of a principalsQuery or rolesQuery for example. Without having to put in the entire vale. > /profile=default/subsystem=security/security-domain=DB_domain:add(authentication=[{"code" => "Database", "flag" => "required", "module-options"=>[("principalsQuery"=>"Select password from UsersTable..... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-427) CLI doesn't read alias from .jbossclirc

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-427?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3824 to WFCORE-427: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-427 (was: WFLY-3824) Affects Version/s: (was: 8.1.0.Final) Component/s: CLI (was: CLI) > CLI doesn't read alias from .jbossclirc > --------------------------------------- > > Key: WFCORE-427 > URL: https://issues.jboss.org/browse/WFCORE-427 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Osamu Nagano > Assignee: Alexey Loubyansky > > By WFLY-1063, a variable can be defined in .jbossclirc and preloaded by CLI. But aliases are not able to define with {{org.jboss.as.cli.CliInitializationException}}. > {code} > $ cat .jbossclirc > set prod_db=/subsystem=datasources/data-source=ExampleDS > alias ll=ls -l > $ $JBOSS_HOME/bin/jboss-cli.sh -c > Unexpected command 'alias ll=ls -l'. Type 'help --commands' for the list of supported commands. > org.jboss.as.cli.CliInitializationException: Failed to process /home/onagano/cases/01180422/wf810/.jbossclirc > at org.jboss.as.cli.impl.CliLauncher.runcom(CliLauncher.java:352) > at org.jboss.as.cli.impl.CommandContextImpl.<init>(CommandContextImpl.java:305) > at org.jboss.as.cli.impl.CommandContextFactoryImpl.newCommandContext(CommandContextFactoryImpl.java:76) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:273) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:253) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:312) > at org.jboss.modules.Main.main(Main.java:460) > {code} > Enclosing by single quote or double quote won't help. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-428) cli - command to add/remove AS modules from non-default module root

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-428?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-2769 to WFCORE-428: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-428 (was: WFLY-2769) Component/s: CLI (was: CLI) > cli - command to add/remove AS modules from non-default module root > ------------------------------------------------------------------- > > Key: WFCORE-428 > URL: https://issues.jboss.org/browse/WFCORE-428 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: swapnesh sharma > Assignee: Alexey Loubyansky > > cli - 'module add/remove' always adds/removes new module in %JOBSS_HOME%/modules directory. > It will be nice to allow add/remove from other default module root directory. Currently only search is allowed for this using JBOSS_MODULEPATH or -mp. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-429?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-2765 to WFCORE-429: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-429 (was: WFLY-2765) Affects Version/s: (was: 8.0.0.CR1) Component/s: CLI Domain Management (was: CLI) (was: Domain Management) Fix Version/s: 1.0.0.Beta1 (was: 9.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.Beta1 > > > (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.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-430) CLI command to list/view AS modules

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-430?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1128 to WFCORE-430: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-430 (was: WFLY-1128) Component/s: CLI (was: CLI) > CLI command to list/view AS modules > ----------------------------------- > > Key: WFCORE-430 > URL: https://issues.jboss.org/browse/WFCORE-430 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Akram Ben Aissi > Assignee: Alexey Loubyansky > > For the same reason as AS7-4265, it would be useful to have command to list and view modules and their configuration. > For example: > modules list --name=org.jboss.* > or simply > modules list > will display a list of all available/installed modules in the AS. > The same way, > modules view --name=org.jboss.as.security --slot=name > will display details for the specified module, include its related resources and classes, and so on -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-424?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-2766 to WFCORE-424: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-424 (was: WFLY-2766) Affects Version/s: (was: 8.0.0.CR1) Component/s: Modules CLI (was: Class Loading) (was: CLI) Fix Version/s: 1.0.0.Beta1 (was: 9.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: Modules, CLI > Reporter: Ondrej Zizka > Assignee: David Lloyd > Fix For: 1.0.0.Beta1 > > > (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.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-425) CLI: include option to specify credentials from file

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-425?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-707 to WFCORE-425: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-425 (was: WFLY-707) Component/s: CLI (was: CLI) Fix Version/s: (was: Awaiting Volunteers) > CLI: include option to specify credentials from file > ---------------------------------------------------- > > Key: WFCORE-425 > URL: https://issues.jboss.org/browse/WFCORE-425 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Radoslav Husar > Priority: Minor > Labels: eap6-ux > > More of a wish-list Jira (hence marked as minor priority and open to community) related to AS7-2036: provide option to specify credentials from file rather than command line, but both are insecure. Users should look into other ways of authenticating against the instance. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-426) Auto more/less in CLI for multi-page output

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-426?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3388 to WFCORE-426: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-426 (was: WFLY-3388) Component/s: CLI (was: CLI) > Auto more/less in CLI for multi-page output > ------------------------------------------- > > Key: WFCORE-426 > URL: https://issues.jboss.org/browse/WFCORE-426 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Darran Lofthouse > Assignee: Alexey Loubyansky > > Where the result of a management operation in the CLI returns multiple screens of output it would be nice if this could be automatically wrapped in a more/less type behaviour. > Similar to how git handles git log compared to how svn handles svn log. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-421) cli tab-completion: filtering out operations not applicable to a resource

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-421?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1116 to WFCORE-421: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-421 (was: WFLY-1116) Component/s: CLI (was: CLI) > cli tab-completion: filtering out operations not applicable to a resource > ------------------------------------------------------------------------- > > Key: WFCORE-421 > URL: https://issues.jboss.org/browse/WFCORE-421 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Environment: JBoss AS 7.0.1 > Reporter: Bill Meyer > Assignee: Alexey Loubyansky > Priority: Minor > > In this example, no Data Sources already exist (clean config). > If I enter the following into the CLI and hit <tab>: > /subsystem=datasources/data-source=:<tab> > I get no operation hints. If I use a bogus resource name that doesn't exist and hit <tab>: > [standalone@localhost:9999 /] /subsystem=datasources/data-source=DoesNotExistDS:<tab> > add disable enable flush-all-connection-in-pool > flush-idle-connection-in-pool read-attribute read-children-names read-children-resources > read-children-types read-operation-description read-operation-names read-resource > read-resource-description remove test-connection-in-pool validate-address > write-attribute > I get all the operations available. This should be made more consistent. The preference, IMO, would be to not have to specify a bogus name and still get the operations list: > [standalone@localhost:9999 /] /subsystem=datasources/data-source=:<tab> > or simpler yet: > [standalone@localhost:9999 /] /subsystem=datasources/data-source:<tab> > (no empty equal sign). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 7 months

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 December 2014