[jboss-jira] [JBoss JIRA] (DROOLS-1235) MBean naming rework

[ https://issues.jboss.org/browse/DROOLS-1235?page=com.atlassian.jira.plugi... ] Matteo Mortari edited comment on DROOLS-1235 at 8/29/16 4:35 AM: ----------------------------------------------------------------- To recap: h6. droolsjbpm-knowledge * Perform necessary Public KIE API changes for allowing API users to specify an optional, unique, container ID. * KieContainer MBean public Kie API on already existing package dedicated for this purpose. h6. drools * give KieContainer an optional user defined name * KieContainer MBean and various refactorings. * jargon: containerId * jargon: configuredReleaseId, resolvedReleaseId * unit testing * assuming the containerId can be "recycled" on dispose. * introducing test for KieServices API with containerId. * avoid using lock and leverage ConcurrentMap without java8 * fixing objectname conventions * there are a few call to internal api / manual call to the implementation constructor new KieContainerImpl from kie-wb-common, optaplanner, etc. the original constructor now creates ID starting with "impl" followed by UUID as a flag. Javadoc notice on all constructors. Please note using the standard public Kie API would create with user-supplied ID or a random UUID normally, transparently. h6. droolsjbpm-integration * KieServer cascade containerId while creating via KieServices * alignment of JON/RHQ drools plugin h6. kie-docs * Including an entry for this on the release notes, as requested. was (Author: tari_manga): To recap: h6. droolsjbpm-knowledge * Perform necessary Public KIE API changes for allowing API users to specify an optional, unique, container ID. * KieContainer MBean public Kie API on already existing package dedicated for this purpose. h6. drools * give KieContainer an optional user defined name * KieContainer MBean and various refactorings. * jargon: containerId * jargon: configuredReleaseId, resolvedReleaseId * unit testing * assuming the containerId can be "recycled" on dispose. * introducing test for KieServices API with containerId. * avoid using lock and leverage ConcurrentMap without java8 * fixing objectname conventions * there are a few call to internal api / manual call to the implementation constructor new KieContainerImpl from kie-wb-common, optaplanner, etc. Original constructor marked with deprecation flag and javadoc notice on all constructors. h6. droolsjbpm-integration * KieServer cascade containerId while creating via KieServices h6. kie-docs * Including an entry for this on the release notes, as requested. -- This message was sent by Atlassian JIRA (v6.4.11#64026)