[
https://jira.jboss.org/browse/ISPN-808?page=com.atlassian.jira.plugin.sys...
]
Richard Achmatowicz commented on ISPN-808:
------------------------------------------
The managermnt and selection of properties for the RemoteCacheManager is spread out over
RemoteCacheManager, ConfigurationProperties and an initial Properties file. If you want to
find out what the full set of properties in effect is, you must interrogate at least
RemoteCacheManager and ConfigurationProperties, but all of the relevant methods are
private.
I was hoping to have access to the ConfigurationProperties file, and not the initial
Properties file. The properties file tells what was passed in by the programmer (which he
already is aware of); the ConfiguratioinProperties file shows for most properties the
values which are actually selected (from initilai properties or defaults) and in effect.
Don't know if it is possible to give access to this.
Otherwise, i'm going to have to resort to workarounds to find out which properties are
in effect, like creating custom versions of everything which spit out information I can
read.
Provide programmatic access to RemoteCacheManager configuration data
--------------------------------------------------------------------
Key: ISPN-808
URL:
https://jira.jboss.org/browse/ISPN-808
Project: Infinispan
Issue Type: Feature Request
Affects Versions: 4.1.0.Final, 4.2.0.CR2
Reporter: Richard Achmatowicz
Assignee: Manik Surtani
Fix For: 4.2.0.CR3, 4.2.0.Final
RemoteCacheManager can have properties passed to it via a number of constructors, but
once the object is constructed, there is no means to view the properties in effect.
At a basic level, just having a getter method for the ConfigurationProperties instance
would be a big help for developers who want to check the properties in effect. This
instance is cuurently private with no hope of access as far as I can tell, even via
reflection.
At a more advanced level, being able to check the set of properties, then stopping,
resetting a property and restarting the RemoteCacheManager instance doesn't seem all
that unreasonable.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira