[
https://jira.jboss.org/jira/browse/TEIID-394?page=com.atlassian.jira.plug...
]
Ramesh Reddy closed TEIID-394.
------------------------------
Resolution: Done
VMControllerID is removed. "Host Name + Process Name" is used as identifier for
any process identification. Previously we had VMName as well as VMId. the hostname and
process combination is unique. So, no need for two separate identifiers for a process.
Also, VM name is overloaded with JVM, all the references to VMName has been changed to
more consistent "Process Name". This way we have single nomenclature when
talking about server processors.
Also, this naming scheme works well with the Admin API based calls, as it was already
using process name.
VMController has verbose interface
----------------------------------
Key: TEIID-394
URL:
https://jira.jboss.org/jira/browse/TEIID-394
Project: Teiid
Issue Type: Task
Components: Common, Console, Server
Affects Versions: 6.0.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.0.0
1) There are several verbose calls that are on the VMController interface, that are not
being used or duplicate.
2) VMContollerID is also super plus and confusing as it does does go with VM/process Name
construct we have
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira