It's probably a source of some confusion that in the JEE world, the driver
isn't pooled, but the data source is. Since the Java Driver for Cassandra
includes the pooling, there's no need for a JEE data source on top of it.
This also means that the Java Driver for Cassandra isn't a one-for-one
exchange with a JDBC driver. I'm not sure if this same level of confusion
occurs with other language drivers for Cassandra.

BTW, as Alex suggested earlier in the thread, this discussion should
probably be moved to the Java Driver mailing list.

Steve

On Fri, Jan 29, 2016 at 1:02 PM, Jack Krupansky <jack.krupan...@gmail.com>
wrote:

> Unfortunately, somebody is likely going to need to educate us in the
> Cassandra community as to what a JBOSS VDB and TEIID really are. For now,
> our response will probably end up being that you should use the Java Driver
> for Cassandra, bypassing any JBOSS/VDB/TEIID support, for now. That TEIID
> link above may shed some light. Otherwise, you'll probably have to ping the
> TEIID community as far as how to configure JBOSS/TEIID. We're here to
> answer questions about Cassandra itself.
>
> -- Jack Krupansky
>
> On Fri, Jan 29, 2016 at 3:42 PM, Corry Opdenakker <co...@bestdata.be>
> wrote:
>
>> What about this cassandra specific howto explained in a recent jboss doc?
>> https://docs.jboss.org/author/display/TEIID/Cassandra+Data+Sources?_sscc=t
>>
>> Im also searching for the real recommended way of connecting to a
>> cassandra db from a jee server, but I didnt found any standard documented
>> solution yet. was a bit surprised that there is not any standard
>> jca/resource archive solution foreseen while Cassandra itself is java
>> based. Maybe I overlooked the info somewhere?
>>
>> Dbcp could help for a large part, but of course one requires a fully
>> reliable production ready solution.
>> https://commons.apache.org/proper/commons-dbcp/
>>
>> Currently I would go for a standard conn pool at app level as is
>> described in the cassandra java driver pdf, knowing that middleware
>> admins don't like that nonstandard jee approach.
>>
>>
>>
>>
>>
>>
>> Op vrijdag 29 januari 2016 heeft Alex Popescu <al...@datastax.com> het
>> volgende geschreven:
>>
>>> I think both of those options expect a JDBC driver, while the DataStax
>>> Java driver is not one.
>>>
>>> As a side note, if you'd provide a more detailed description of the
>>> setup you want to get and post it to the Java driver mailing list
>>> https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user,
>>> chances of getting an answer will be higher.
>>>
>>> On Fri, Jan 29, 2016 at 9:56 AM, KAMM, BILL <wk1...@att.com> wrote:
>>>
>>>> I’m just getting started with Cassandra, and am trying to integrate it
>>>> with JBoss.  I’m configuring the standalone-ha-full.xml file, but don’t
>>>> know what to use for the driver class.  For example, I have this:
>>>>
>>>>
>>>>
>>>> <drivers>
>>>>
>>>>     <driver name="cassandra" module="com.abc.xyz.jboss.cassandra">
>>>>
>>>>         <driver-class>com.datastax.driver.core.xxxxxxxx</driver-class>
>>>>
>>>>     </driver>
>>>>
>>>> </drivers>
>>>>
>>>>
>>>>
>>>> What do I replace “xxxxxxxx” with?
>>>>
>>>>
>>>>
>>>> Is “com.datastax.driver.core” even correct, or am I going down the
>>>> wrong path?  I am using the DataStax 2.0.2 driver, with Cassandra 2.0.8.
>>>>
>>>>
>>>>
>>>> Should I be using <datasource-class> instead of <driver-class>?
>>>>
>>>>
>>>>
>>>> Does anybody have a working example they can share?  Any help to get me
>>>> going would be appreciated.  Thanks.
>>>>
>>>>
>>>>
>>>> Bill
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Bests,
>>>
>>> Alex Popescu | @al3xandru
>>> Sen. Product Manager @ DataStax
>>>
>>>
>>
>> --
>> ----------------------------------
>> Bestdata.be
>> Optimised ict
>> Tel:+32(0)496609576
>> co...@bestdata.be
>> ----------------------------------
>>
>>
>


-- 
Steve Robenalt
Software Architect
sroben...@highwire.org <bza...@highwire.org>
(office/cell): 916-505-1785

HighWire Press, Inc.
425 Broadway St, Redwood City, CA 94063
www.highwire.org

Technology for Scholarly Communication

Reply via email to