Mailing-List: contact dev-help@quarks.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@quarks.incubator.apache.org
Date: Fri, 22 Apr 2016 16:24:12 +0000 (UTC)
From: "Dale LaBossiere (JIRA)" <jira@apache.org>
To: dev@quarks.incubator.apache.org
Message-ID: <JIRA.12961717.1461342231000.9732.1461342252958@Atlassian.JIRA>
In-Reply-To: <JIRA.12961717.1461342231000@Atlassian.JIRA>
References: <JIRA.12961717.1461342231000@Atlassian.JIRA>
 <JIRA.12961717.1461342231624@arcas>
Subject: [jira] [Created] (QUARKS-154) ControlService "type"
 rules/conventions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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)