]
Tristan Tarrant updated ISPN-2957:
----------------------------------
Status: Pull Request Sent (was: Reopened)
Git Pull Request:
CustomInterceptor configuration is incomplete and buggy
-------------------------------------------------------
Key: ISPN-2957
URL:
https://issues.jboss.org/browse/ISPN-2957
Project: Infinispan
Issue Type: Bug
Components: Configuration, Core API
Affects Versions: 5.2.1.Final
Reporter: Alan STS
Assignee: Tristan Tarrant
Fix For: 5.3.0.Final
Infinispan 5.2 schema allows to declare a custom interceptor with properties as follows:
<customInterceptors>
<interceptor position="LAST"
class="com.group.awms.is.resource.dao.infinispan.interceptor.ApplicationInterceptor">
<properties>
<property name="cacheActivityName" value="activity"
/>
</properties>
</interceptor>
</customInterceptors>
Problem is that method parseInterceptor of class Parser52 does not expect any content for
interceptors and the following exception is raised:
Message: Unexpected element '{urn:infinispan:config:5.2}properties' encountered
at
org.infinispan.configuration.parsing.ParseUtils.unexpectedElement(ParseUtils.java:57)
at
org.infinispan.configuration.parsing.ParseUtils.requireNoContent(ParseUtils.java:152)
at org.infinispan.configuration.parsing.Parser52.parseInterceptor(Parser52.java:1186)
at
org.infinispan.configuration.parsing.Parser52.parseCustomInterceptors(Parser52.java:1148)
at org.infinispan.configuration.parsing.Parser52.parseCache(Parser52.java:156)
at org.infinispan.configuration.parsing.Parser52.parseNamedCache(Parser52.java:139)
at org.infinispan.configuration.parsing.Parser52.readElement(Parser52.java:106)
at org.infinispan.configuration.parsing.Parser52.readElement(Parser52.java:75)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:77)
... 40 more
The Parser class is not in sync with the schema.
--
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: