Re: [JBoss-dev] JDBC provider redundant and XA stuff

[Bill B. <wb...@co...>]

Hey Filip,

Take a look at the XADataSourceLoader code.  It uses a Minerva 
XAPoolDataSource.  getConnection() uses the Minerva code base to 
register the transaction with the JBoss transaction manager.  There is 
no code anywhere except in Minerva that registers the XAResources with 
the Transaction Manager that I can find.  Please tell me that I'm wrong.

Bill

Filip Hanik wrote:

> I thought that was already in place.
> Minerva was only used for non XA datasources, so I assumed the developers of
> JBoss already has implemented the support for real XA datasources.
> 
> maybe I was wrong :)
> 
> Filip
> 
> ~
> Namaste - I bow to the divine in you
> ~
> Filip Hanik
> Software Architect
> fi...@fi...
> www.filip.net
> 
>> -----Original Message-----
>> From: jbo...@li...
>> [mailto:jbo...@li...]On Behalf Of Bill
>> Burke
>> Sent: Thursday, March 29, 2001 9:08 AM
>> To: marc fleury
>> Cc: Jboss-Development@Lists. Sourceforge. Net
>> Subject: Re: [JBoss-dev] JDBC provider redundant and XA stuff
>> 
>> 
>> One more thing on this that I've commented on before.
>> 
>> The Oracle 8.1.7 drivers do connection and statement pooling as well as
>> XAConnections, so there is no need to use Minerva.  Unfortunately,
>> Minerva does all the work of hooking up the XAResources with the
>> Transaction Manager and such.  It would be nice if there was some
>> XADataSourceLoader framework so that developers could write optimized
>> driver specific datasources that can connect up to JBoss's connection
>> manager and be their own connection pool.  Am I making any sense here?
>> 
>> Anyways, I'm very interested in putting together this simple "framework"
>> and writing an Oracle 8.1.7 specific JBoss DataSource, and, if you want
>> I would also clean up the JDBCProvider stuff you talked about.
>> Let me know.
>> 
>> Bill
>> 
>> P.S.  I know I'm new here, and there's a trust factor involved, but I'm
>> serious about contributing to any JBoss effort.
>> 
>> 
>> 
>> marc fleury wrote:
>> 
>>> Guys, (Aaron, Rickard)
>>> 
>>> Looking at the jdbc configuration and packages.
>>> 
>>> If I understand the JDBCProvider class well, it is about 80
>> 
>> lines of code
>> 
>>> that does essentially one thing
>>> 
>>> Class.forName("driver");
>>> 
>>> With a fancy MBean structure around it.  Also the usage of the
>>> System.get/setProperty is strange (useless).
>>> 
>>> On the other hand it requires the fairly complex JDBC MBean
>> 
>> structure in the
>> 
>>> configuration files.
>>> 
>>> Then when I look at the parameters passed to the
>> 
>> XADataSourceLoader, there
>> 
>>> is a TON of stuff that is never modified, and frankly could go
>> 
>> as defaults
>> 
>>> in the codebase.
>>> 
>>> I therefore propose the following
>>> 
>>> 1- Axe the JDBCProvider class
>>> 2- Add the "Driver" property to the XADataSource class and let
>> 
>> IT initialize
>> 
>>> (I am talking about the jboss classes)
>>> 3- Put the defaults in the class so that if you don't specify
>> 
>> anything in
>> 
>>> XML, it still works.
>>> 
>>> >From an admin standpoint we will be able to make sense of the
>> 
>> jboss.jcml
>> 
>>> mbeans and that is a step in the right direction, also it will
>> 
>> mean that we
>> 
>>> will be able to add dbs dynamically (with a differential driver
>>> specification)
>>> 
>>> I don't know... any howlers out there?
>>> 
>>> marc
>>> 
>>> _________________
>>> Marc Fleury, Ph.D
>>> ma...@jb...
>>> _________________
>>> 
>>> 
>>> _______________________________________________
>>> Jboss-development mailing list
>>> Jbo...@li...
>>> http://lists.sourceforge.net/lists/listinfo/jboss-development
>>> 
>>> 
>>> 
>> 
>> 
>> _______________________________________________
>> Jboss-development mailing list
>> Jbo...@li...
>> http://lists.sourceforge.net/lists/listinfo/jboss-development
>>