[jboss-jira] [JBoss JIRA] Commented: (AS7-757) Provide an operation to distinguish domain & standalone

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/AS7-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605543#comment-12605543 ] 

Brian Stansberry commented on AS7-757:
--------------------------------------

http://github.com/jbossas/jboss-as/compare/f896151...800eecb

adds:

1) On the root resource, whether, attribute "process-type"

returns "Server", "Domain Controller", "Host Controller", depending on whether the client has connected to a standalone server, a host controller that is acting as the Domain Controller, or a Host Controller that is acting is not the DC. (Note that reading the root resource will fail in the 3rd case, which is a separate issue that needs to be tidied up.)

2) On the root resource for a server (either the root on a standalone mode server or /host=x/server=y in domain mode), attribute "launch-type"

returns DOMAIN, STANDALONE or EMBEDDED, depending on whether an HC launched the server process, the server process was launched from the cmd line, or the server is running embedded in an application.

3) On the host=x resource for a host, attribute "master" which returns true or false depending on whether the host is acting as the domain controller.

These can be played around with.

> Provide an operation to distinguish domain & standalone
> -------------------------------------------------------
>
>                 Key: AS7-757
>                 URL: https://issues.jboss.org/browse/AS7-757
>             Project: Application Server 7
>          Issue Type: Enhancement
>          Components: Domain Management
>            Reporter: Heiko Braun
>            Assignee: Brian Stansberry
>             Fix For: 7.0.0.CR1
>
>
> The console bootstraps form the domain model. It automatically decides to either launch the standalone or domain view. Currently we are checking for a top level "subsystem" element which only exists in standalone mode:
> {
> [INFO]     "operation" => "read-children-names",
> [INFO]     "child-type" => "subsystem",
> [INFO]     "address" => []
> [INFO] }
> However this operation logs an error on the server side when running the domain mode:
> [Host Controller] 15:40:15,052 WARN  [org.jboss.as.controller] (HttpManagementService-threads - 9) operation ("read-children-names") failed - address: ([]): org.jboss.as.controller.OperationFailedException
> [Host Controller] 	at org.jboss.as.controller.operations.global.GlobalOperationHandlers$ReadChildrenNamesOperationHandler.execute(GlobalOperationHandlers.java:304)
> [Host Controller] 	at org.jboss.as.domain.controller.operations.ReadChildrenNamesHandler.execute(ReadChildrenNamesHandler.java:65)
> In order to cleanup this bootstrap procedure and to remove the server side error, a custom operation to distinguish the two execution modes would be helpful.
> i.e. 
> :get-meta-data()
> {
>   "mode" => "standalone",
>   "api-version" => "1.0",
>   "some" => "other value"
> }

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira