4 Replies Latest reply on Nov 11, 2014 2:17 AM by virchete

    Infinispan 6 changes xml schema

    virchete

      Hi, I am migrating from infinispan 5.X to infinispan 6.0.2.Final (the one used in wildfly).

       

      <?xml version="1.0" encoding="UTF-8"?>

      <infinispan

         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

         xsi:schemaLocation="urn:infinispan:config:6.0 http://docs.jboss.org/infinispan/schemas/infinispan-config-6.0.xsd

                             urn:infinispan:config:jdbc:6.0 http://docs.jboss.org/infinispan/schemas/infinispan-cachestore-jdbc-config-6.0.xsd"

         xmlns="urn:infinispan:config:6.0"

         xmlns:jdbc="urn:infinispan:config:jdbc:6.0" >

          <global>

          </global>

       

          <default>

          </default>

       

          <namedCache name="sramp">

              <loaders passivation="false" shared="false" preload="false">

                  <jdbc:stringKeyedJdbcStore xmlns="urn:infinispan:config:jdbc:5.2"

                      fetchPersistentState="true" ignoreModifications="false" purgeOnStartup="false">

                   

                    <jdbc:dataSource jndiUrl="java:comp/env/jdbc/sramp" xmlns="urn:infinispan:config:jdbc:5.2"/>

                    <stringKeyedTable

                     dropOnExit="false" createOnStart="true" prefix="ISPN_STRING_TABLE">

                      <idColumn name="ID_COLUMN" type="VARCHAR(255)" />

                      <dataColumn name="DATA_COLUMN" type="BINARY" />

                      <timestampColumn name="TIMESTAMP_COLUMN" type="BIGINT" />

                    </stringKeyedTable>

                  </jdbc:stringKeyedJdbcStore>

              </loaders>

              <transaction

                  transactionManagerLookupClass="org.infinispan.transaction.lookup.DummyTransactionManagerLookup"

                  transactionMode="TRANSACTIONAL" lockingMode="PESSIMISTIC" />

                 

          </namedCache>

       

      </infinispan>

       

      This xml (with the headers pointing to the schemas of 5.2 was working in that version of infinispan. In 6.2 it seems that  the "loaders" tag inside of the namedCache tag has dissapeared. Could you explain me what is the way to do the equivalent in infinispan 6?

       

      Thanks

      David

      Jboss Overlord Team.

        • 1. Re: Infinispan 6 changes xml schema
          rvansa

          Now it's called 'persistence', the rest of configuration is more-or less the same.

           

          However, as you already migrate, you should consider using Infinispan 7.0 which was released few days ago. There, the configuration layout had undergone bigger changes as we've tried to get the library mode configuration closer to those in server mode (WildFly).

          • 2. Re: Infinispan 6 changes xml schema
            virchete

            I would like to use the last version of your product, if it is possible.

             

            I want to know the implications it could have. We are trying to be inline with wildfly 8.1 libraries. As i have seen, it is used there infinispan 6.0.2.final.

             

            Also we are using modeshape 4.0.0.Final.

             

            Is it compatible infinispan 7.0 with modeshape 4?

             

            Thanks

            David

            • 3. Re: Infinispan 6 changes xml schema
              rhauch

              The ModeShape community has not looked at Infinispan 7, which was released just recently. Supposedly there are no API changes, but the configuration file format is very different in Infinispan 7. Regardless, we've not yet tried to build or run against Infinispan 7.

               

              ModeShape 4.0.0.Final (the last release) was built against Infinispan 6.0.2.Final.

              • 4. Re: Infinispan 6 changes xml schema
                virchete

                Then for the moment we need to stick to the 6.0.2.Final version unfortunately.