[jira] [Updated] (EDGENT-154) ControlService "type" rules/conventions

["Dale LaBossiere (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/EDGENT-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dale LaBossiere updated EDGENT-154:
-----------------------------------
    Component/s: API

> ControlService "type" rules/conventions
> ---------------------------------------
>
>                 Key: EDGENT-154
>                 URL: https://issues.apache.org/jira/browse/EDGENT-154
>             Project: Edgent
>          Issue Type: Task
>          Components: API
>            Reporter: Dale LaBossiere
>            Priority: Minor
>
> ControlService is documented as being usable by applications (as well as Quarks).  
> Its documentation needs to be improved so applications know the rules/conventions for choosing "type" values they register their mbeans with so as to avoid collisions - e.g., with the values that the runtime is using.  Right now the runtime isn't doing anything to qualify the type names it's using (e.g., "job").
> Rules/conventions for "identifier" values are also needed for avoiding collisions.  e.g., runtime uses JOB_<n>  Also need to clarify if it's legal for multiple registrations (different beans) for the same "id" and/or alias.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)