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
[EMAIL PROTECTED]
_________________


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to