[
https://issues.jboss.org/browse/ISPN-948?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-948:
----------------------------------
Fix Version/s: (was: 4.2.1.FINAL)
This definitely won't make the 4.x series, we're primarily fixing bugs there now.
Wrt the JPA case, apps don't have access to the CacheManager, so doubt that even such
API would be useful. JMX capabilities to view the cache configuration would be handier
here.
Maybe this is something you could look into contribute yourself? :)
Support XML marshaling of Configuration instances
-------------------------------------------------
Key: ISPN-948
URL:
https://issues.jboss.org/browse/ISPN-948
Project: Infinispan
Issue Type: Feature Request
Components: Configuration
Affects Versions: 4.2.1.CR3
Reporter: Jürgen Kellerer
Assignee: Manik Surtani
Fix For: 5.0.0.Final
Original Estimate: 4 hours
Remaining Estimate: 4 hours
Infinispan supports a very flexible way of configuring caches using multiple levels of
inheritance.
While this is really nice, it is sometimes not easy to understand how exactly a
particular cache was configured.
(E.g. JPA is just one example where a cache configuration can be adjusted in several
ways).
JMX or debuggers help but may not always be available.
What about allowing to convert a configuration instance back to XML to give a quick
overview of the really applied settings. _(Optionally it might also be a nice little
feature to implement a "toXmlString();" method or override the default and also
make this available through JMX)_
JAXB annotations are already present on all configurable options but a couple getters and
a @XmlRootElement annotation is missing that would allow to convert an existing instance
back to XML. The effort in doing this should be rather low.
---
This feature request may also fit with #ISPN-791 as it would allow to transfer cache
configs using XML.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira