You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@edgent.apache.org by "Dale LaBossiere (JIRA)" <ji...@apache.org> on 2016/04/22 18:24:12 UTC

[jira] [Created] (QUARKS-154) ControlService "type" rules/conventions

Dale LaBossiere created QUARKS-154:
--------------------------------------

             Summary: ControlService "type" rules/conventions
                 Key: QUARKS-154
                 URL: https://issues.apache.org/jira/browse/QUARKS-154
             Project: Quarks
          Issue Type: Task
            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.4#6332)