Hi all,
Sebastian recently added BCHMV8 resizing and I'm now hooking it up to configuratiombean jmx and server. I wanted your opinion on some details.
- configuration: easy, register a listener with the attribute so that invoking configuration.eviction().size (newSize) does a resize of the data container
- server already exposes the size in the management model, we just need to change its behaviour so that the change is "live". In this context the change is also persisted to the xml configuration
- Jmx: do we want a writable "capacity" attribute or a resize operation? And do we want it on the cache mbean or on a new data container mbean? And should the change affect the configuration object too, i.e. invoking configuration.eviction().size () should return the new value? For symmetry with server we should.
Tristan