[
https://issues.jboss.org/browse/ISPN-5950?page=com.atlassian.jira.plugin....
]
Radim Vansa commented on ISPN-5950:
-----------------------------------
Generally speaking, Parser should parse the XML, but it should *not* contain any logic. If
we can't make the configuration straight, any steps like 'this combo of attributes
implies these defaults for other attributes' should get into
xConfigurationBuilder.build().
Parser sets transaction().useSynchronization to non-default value
-----------------------------------------------------------------
Key: ISPN-5950
URL:
https://issues.jboss.org/browse/ISPN-5950
Project: Infinispan
Issue Type: Bug
Components: Configuration
Affects Versions: 8.0.1.Final
Reporter: Radim Vansa
Default value for transaction().useSynchronization() is false, so when the configuration
is build programmatically, it is set to false. However, if I configure a non-transactional
cache in XML and read the configuration, it is set to true.
This complicates testing, when I want to compare programmatic and XML configurations, and
generally it is inconsistent.
When doing equals() operation on configurations. transaction-only attributes should not
be compared if transactionMode == NONE, since they actually don't matter.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)