edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Created] (QUARKS-154) ControlService "type" rules/conventions
Date Fri, 22 Apr 2016 16:24:12 GMT
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

View raw message