3 Replies Latest reply on Oct 4, 2012 11:14 AM by shawkins

    Is there a need for an Infinispan-connector?

    van.halbert

      The more I setup and install and try to create a quick start, the more I'm thinking it would just be easiser if there was a connector-infinispan.

       

      Why?  The first pain is getting the CacheContainer bound into JNDI.    If I take the time to implement ObjectFactory in order to bind the container, why not go ahead and create a connector that can reused and easier to bind to cache.  Also, this will make it easier to create a new cache and bind to JNDI (then this logic can be moved out of the translator). 

       

      Is there a better option than creating the connector?

        • 1. Re: Is there a need for an Infinispan-connector?
          shawkins

          To make sure I understand what you are saying, to rephase what we have are the following translators:

           

          Infinispan

          -lucene

          -key

          InfinispanRemote

          MapCache

           

          What you are getting at, which we want is:

           

          Map

          Infinispan - likely an extension of Map where whether to use lucence is based upon the table metadata and perhaps even the query (for example if only equi primary key criteria is specified, then it should be better to query the cache rather than use lucene).

           

          All of the other concerns about cache lookup should be abstracted - either through a ResourceAdapter, JNDI, or container service injection.

          • 2. Re: Is there a need for an Infinispan-connector?
            van.halbert

            Currently, to my knowledge, there isn't a ResourceAdapter , which is what I'm proposing creating (i.e., infinispan-connector).

            • 3. Re: Is there a need for an Infinispan-connector?
              shawkins

              So now the current state reflects two translator types using a common connection interface ObjectConnection.  We'll develop the connection strategies for that on the TEIID-2210 issue.