[jboss-jira] [JBoss JIRA] Commented: (JGRP-188) JGroups should not use System properties, because it's too restrictive
[ http://jira.jboss.com/jira/browse/JGRP-188?page=comments#action_12340936 ]
Bela Ban commented on JGRP-188:
-------------------------------
I don't think this will fly, as other systems such as JBoss use System.setProperty()
*after* the VM has been started, and we have no way of intercepting this ! And we cannot
force users to use GlobalConfigurator.setProperty().
I'm therefore rejecting this issue, if you have a solution to the above problem,
please feel free to re-open the case.
JGroups should not use System properties, because it's too
restrictive
----------------------------------------------------------------------
Key: JGRP-188
URL: http://jira.jboss.com/jira/browse/JGRP-188
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.2.9.1, 2.2.9, 2.2.8
Environment: all
Reporter: Robert Stevenson
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.4
Original Estimate: 1 day
Remaining Estimate: 1 day
JGroups should not use System properties for configuration, it should instead use a
Global Configurator class (singleton), similar to log4j; which just contains a Properties
object. This would allow JGroups to be much easier to move around to different
environments. For example : (Applet), which does not have access to easily change System
properties, on a per applet basis.
This new class could have a mapping/conversion method to make the current -D command line
options be put into this new Properties Configurator for backward compatibility
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira