![]() |
|
|
|
|
Change By:
|
Roman Kovařík
(05/Feb/15 12:52 PM)
|
|
Description:
|
# Register
{{
cacheManager}} with context path.
# Verify if we still need to load defaults from ehcache-failsafe.xml
In {{
info.magnolia.module.cache.ehcache.EhCacheFactory#start}}
:
We register {{CacheManager}} with proper name since MGNLCACHE-60. Because of this
we
do
cannot register a new manager with updated configuration (
{{
ConfigurationFactory
net
.
parseConfiguration
sf.ehcache.management.ManagementService#registerMBeans}}).
At least some of the properties should be configurable at runtime
(
see {{net.sf.ehcache.config.Configuration.DynamicProperty}}
)
. The change of {{defaultCacheConfiguration
}}
, which
is
meant to load ehcache default configuration in case we have none. While this *might* be interesting
enough
for
users who'd want
us.
Not sure how
to
have an xml based
change the
configuration
, this seems counter-intuitive with our tree-based configuration
of an existing manager
.
We could test:
Besides, when there is no specific xml configuration, ehcache fallbacks on its
-
{{
ehcache-failsafe
cacheManager = CacheManager
.
xml
create(cfg);
}}
file, which :
-
logs a warning about not finding configuration, which is confusing
{{cacheManager.getConfiguration
(
since there IS configuration, we just haven't tried loading it yet
)
.setDefaultCacheConfiguration()}}
-
only sets up a default cache config and a disk store path - and we always reconfigure both of these
.
..
|
|
Component/s:
|
configuration
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
