[
https://issues.jboss.org/browse/ISPN-1226?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1226:
----------------------------------------
@Mark, what's the issue/exception that you're having with customInterceptors being
defined in a named cache? We have a test XML file that contains such configuration in a
named test cache
(
https://github.com/infinispan/infinispan/blob/master/core/src/test/resour...)
and we have several tests that verify that the file can be parsed (XmlFileParsingTest),
that a new cache manager can be created out of it
(CacheManagerXmlConfigurationTest)...etc. If you could provide a unit test (check the
https://docs.jboss.org/author/display/ISPN/Infinispan+Maven+Archetypes for a skeleton for
such UT) that'd be great.
Certain configuration elements not read correctly
-------------------------------------------------
Key: ISPN-1226
URL:
https://issues.jboss.org/browse/ISPN-1226
Project: Infinispan
Issue Type: Bug
Components: Configuration
Affects Versions: 5.0.0.CR7
Environment: n/a
Reporter: Mark Addy
Assignee: Galder Zamarreño
Priority: Critical
Labels: configuration
Fix For: 5.0.0.FINAL
I am unable to create a custom interceptor for a specific NamedCache via xml
configuration.
The only solution using external configuration is to add the <customInterceptors>
element to the <default> cache - but this applies the interceptor to all caches.
<customInterceptors>
<interceptor after="org.infinispan.interceptors.CallInterceptor"
class="com.test.MyCustomInterceptor" />
</customInterceptors>
Programmatic configuration works in Embedded mode but this can't be used with hotrod
as calling getAdvancedCache() results in an UnsupportedOperationException.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira