12:18 p.m.
:read-resource should also show r/w status and whether restart is required
--------------------------------------------------------------------------
Key: AS7-2333
URL: https://issues.jboss.org/browse/AS7-2333
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Affects Versions: 7.1.0.Alpha1
Environment: all
Reporter: Rich Sharples
Assignee: Alexey Loubyansky
Fix For: 7.1.0.Beta1
:read-resource could provide some more useful information :
some attributes can't be changed (eg. they are ports generated from an offset) -
:read-resource output should show the attributes that are read-only.
some attributes require a restart to take effect - :read-resource should make this clear.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:50 a.m.
[
https://issues.jboss.org/browse/AS7-2333?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-2333:
----------------------------------
Assignee: Brian Stansberry (was: Alexey Loubyansky)
Fix Version/s: (was: 7.1.0.Beta1)
Component/s: Domain Management
(was: CLI)
This isn't really a CLI issue; it's a core management API issue.
I disagree that read-resource should provide this; you're requesting a mix of metadata
about state and the state itself. The metadata can be obtained via the
read-resource-description operation.
I can see the desire for seeing both types of data in some combined format, but it needs
to be a separate operation.
From a practical point of view, changing the existing operation would
break every client that exists (console, JON, deployment-scanner, probably CLI features,
custom stuff done by others that I don't know about).
:read-resource should also show r/w status and whether restart is
required
--------------------------------------------------------------------------
Key: AS7-2333
URL: https://issues.jboss.org/browse/AS7-2333
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.Alpha1
Environment: all
Reporter: Rich Sharples
Assignee: Brian Stansberry
Labels: eap6-ux
:read-resource could provide some more useful information :
some attributes can't be changed (eg. they are ports generated from an offset) -
:read-resource output should show the attributes that are read-only.
some attributes require a restart to take effect - :read-resource should make this clear.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:54 a.m.
[
https://issues.jboss.org/browse/AS7-2333?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-2333:
----------------------------------------
These kind of issues have to submitted for CLI commands. I guess, people are just
confused.
:read-resource should also show r/w status and whether restart is
required
--------------------------------------------------------------------------
Key: AS7-2333
URL: https://issues.jboss.org/browse/AS7-2333
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.Alpha1
Environment: all
Reporter: Rich Sharples
Assignee: Brian Stansberry
Labels: eap6-ux
:read-resource could provide some more useful information :
some attributes can't be changed (eg. they are ports generated from an offset) -
:read-resource output should show the attributes that are read-only.
some attributes require a restart to take effect - :read-resource should make this clear.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:58 a.m.
[
https://issues.jboss.org/browse/AS7-2333?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-2333:
---------------------------------------
This kind of thing could potentially be done via a high level CLI command that merges and
formats content, and not a new server-side operation. If you want to assign it to
yourself, Alexey, feel free. We need to be careful about high level commands that are
kinda-sorta the same as low level commands, but are different. We need to be careful that
things remain intuitive.
:read-resource should also show r/w status and whether restart is
required
--------------------------------------------------------------------------
Key: AS7-2333
URL: https://issues.jboss.org/browse/AS7-2333
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.Alpha1
Environment: all
Reporter: Rich Sharples
Assignee: Brian Stansberry
Labels: eap6-ux
:read-resource could provide some more useful information :
some attributes can't be changed (eg. they are ports generated from an offset) -
:read-resource output should show the attributes that are read-only.
some attributes require a restart to take effect - :read-resource should make this clear.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:04 a.m.
[
https://issues.jboss.org/browse/AS7-2333?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-2333:
----------------------------------------
I have a few issues to look into. But after that, I'm gonna add commands for
describing/reading resources in a friendlier format, so this could be included.
:read-resource should also show r/w status and whether restart is
required
--------------------------------------------------------------------------
Key: AS7-2333
URL: https://issues.jboss.org/browse/AS7-2333
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.Alpha1
Environment: all
Reporter: Rich Sharples
Assignee: Brian Stansberry
Labels: eap6-ux
:read-resource could provide some more useful information :
some attributes can't be changed (eg. they are ports generated from an offset) -
:read-resource output should show the attributes that are read-only.
some attributes require a restart to take effect - :read-resource should make this clear.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:46 p.m.
[
https://issues.jboss.org/browse/AS7-2333?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-2333:
----------------------------------
Assignee: Alexey Loubyansky (was: Brian Stansberry)
Fix Version/s: 7.1.0.CR1
Component/s: CLI
I'm converting this to a CLI issue and marking it for CR1 just as an indication
we'd like to have it done in 7.1./EAP 6.0. But Alexey please let me know if you feel
that is not doable. We are doing a triage of what can and can't make it into 7.1/EAP
6.0.
:read-resource should also show r/w status and whether restart is
required
--------------------------------------------------------------------------
Key: AS7-2333
URL: https://issues.jboss.org/browse/AS7-2333
Project: Application Server 7
Issue Type: Feature Request
Components: CLI, Domain Management
Affects Versions: 7.1.0.Alpha1
Environment: all
Reporter: Rich Sharples
Assignee: Alexey Loubyansky
Labels: eap6-ux
Fix For: 7.1.0.CR1
:read-resource could provide some more useful information :
some attributes can't be changed (eg. they are ports generated from an offset) -
:read-resource output should show the attributes that are read-only.
some attributes require a restart to take effect - :read-resource should make this clear.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:21 a.m.
[
https://issues.jboss.org/browse/AS7-2333?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky resolved AS7-2333.
------------------------------------
Fix Version/s: 7.1.0.CR1
(was: 7.1.0.Final)
Resolution: Done
I am resolving this issue. Although, it's not been fixed as requested, there is
another way of getting this info.
There won't be changes to these *operations*.
Now about the way this info is supposed to be provided to the user (you find it not
convenient then feel free to create issues for this).
There is read-attribute *command*. Which by default returns just the value. But it also
has --verbose mode which will display all the information available in model description
for the given property. E.g.
[standalone@localhost:9999 /] read-attribute name --verbose
access-type read-write
description The name of this server. If not set, defaults to the runtime value of
InetAddress.getLocalHost().getHostName().
min-length 1
nillable true
required false
restart-required no-services
storage configuration
type STRING
value tstudio
This is for a specific attribute. You can also use 'ls -l' which be default will
display a table of attributes (and children) showing their names, types and values. You
can extend the default columns by specifying properties you want to see by prefixing them
with '--'. E.g.
[standalone@localhost:9999 /] ls -l --restart-required
ATTRIBUTE VALUE TYPE RESTART-REQUIRED
launch-type STANDALONE STRING n/a
name tstudio STRING no-services
namespaces [] OBJECT n/a
process-type Server STRING n/a
profile-name undefined STRING n/a
release-codename Tesla STRING n/a
release-version 7.1.0.CR1-SNAPSHOT STRING n/a
running-mode NORMAL n/a n/a
schema-locations [] OBJECT n/a
server-state running STRING n/a
:read-resource should also show r/w status and whether restart is
required
--------------------------------------------------------------------------
Key: AS7-2333
URL: https://issues.jboss.org/browse/AS7-2333
Project: Application Server 7
Issue Type: Feature Request
Components: CLI, Domain Management
Affects Versions: 7.1.0.Alpha1
Environment: all
Reporter: Rich Sharples
Assignee: Alexey Loubyansky
Labels: eap6-ux
Fix For: 7.1.0.CR1
:read-resource could provide some more useful information :
some attributes can't be changed (eg. they are ports generated from an offset) -
:read-resource output should show the attributes that are read-only.
some attributes require a restart to take effect - :read-resource should make this clear.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:25 a.m.
[
https://issues.jboss.org/browse/AS7-2333?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-2333:
----------------------------------------
I should mention that unfortunately tab-completion for the supported properties after
'ls -l' is not yet supported. It deserves a jira issue and will be fixed later.
:read-resource should also show r/w status and whether restart is
required
--------------------------------------------------------------------------
Key: AS7-2333
URL: https://issues.jboss.org/browse/AS7-2333
Project: Application Server 7
Issue Type: Feature Request
Components: CLI, Domain Management
Affects Versions: 7.1.0.Alpha1
Environment: all
Reporter: Rich Sharples
Assignee: Alexey Loubyansky
Labels: eap6-ux
Fix For: 7.1.0.CR1
:read-resource could provide some more useful information :
some attributes can't be changed (eg. they are ports generated from an offset) -
:read-resource output should show the attributes that are read-only.
some attributes require a restart to take effect - :read-resource should make this clear.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5337
days inactive
5388
days old
7 comments
5 participants
participants (5)
-
Alexey Loubyansky (Commented) (JIRA) -
Alexey Loubyansky (Resolved) (JIRA)
-
Brian Stansberry (Commented) (JIRA)
-
Brian Stansberry (Updated) (JIRA)
-
Rich Sharples (Created) (JIRA)