The XML for a JDBC Cache Store is its own XML Schema, as referenced in the community doc here: Search for "multiple XML schemas" http://infinispan.org/docs/6.0.x/user_guide/user_guide.html This documentation needs to be added to the enterprise documentation. Without adding the appropriate cache store XML namespace/schema to your cache configuration, you will get XML parse errors.
In the 6.2 Admin Guide, Chapter has gives XML configurations that will not work without making the change to include multiple XML Schemas. For a specific example look at 15.2.2. JdbcStringBasedStore Configuration (Library Mode)
The multiple XML schemas seems to be added in JDBC cache store Library configurations and not in server mode configs. The header of server mode configuration remains the same for configs with and without JDBC configured. John, am I correct with what I stated above? Also, there is no schemas found in 6.3 related ISPN repo. So I assume that this is not relevant for JDG 6.3. So my 2 queries are: 1. Should the multiple XML schemas be added in server mode configs as well? 2. Should the multiple XML schemas be added in JDG 6.3 docs or only in 6.2?
I have resumed office from today. I consulted with Tomas about this and he will provide his findings about adding the XML schemas in 6.3 JDBC configs later today.
Hey Bobb, I've confirmed working configuration for both JDG 6.2 and 6.3. Into header: <infinispan xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:infinispan:config:6.0 http://www.infinispan.org/schemas/infinispan-config-6.0.xsd urn:infinispan:config:jdbc:6.0 http://www.infinispan.org/schemas/infinispan-cachestore-jdbc-config-6.0.xsd" xmlns="urn:infinispan:config:6.0"> And add xmlns="urn:infinispan:config:jdbc:6.0" definition into specific jdbc cache store element -- like this: <stringKeyedJdbcStore xmlns="urn:infinispan:config:jdbc:6.0" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false" key2StringMapper="org.infinispan.loaders.keymappers.DefaultTwoWayKey2StringMapper"> This configuration works for me with both 6.1.1.ER1-redhat-1 and 6.0.3.Final-redhat-3. Hope that helps. Tomas
Hey Misha, could you please brew this and push it live?
I'll push the 6.2.1 changes now and the 6.3 ones will go out with the async update so we'll close off this bug once both are released.
Created ticket.
This content is now available on https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Grid/