[Wsf-general] Data service - Connection

[James Clark]

> <connection dbtype="mysql|derby|sqlserver">

Not a good approach. The relevant properties can potentially depend on
things other than the type of database.  For example, a property that
specifies the JDBC driver is relevant iff you're using JDBC. A
particular database may be accessed in multiple ways: MySQL could be
accessed natively, via ODBC or via JDBC.  It should be possible to use
JDBC generically without knowing which database you are connecting to.

I suggest instead that property names that are not generic should be
qualified to indicate their applicability, e.g. "jdbc.driver" for the
JDBC driver, "user" for the username (because that's generic), or
"mysql.option-group-suffix" to specify the MySQL option group suffix.

> And as an initial stage i think we should support mysql for axis2/c and
> for axis2 its derby.

That's probably a good starting point.  But in doing the design, we need
to think beyond the initial stage and consider what we ultimately want
to support.  For Axis2/C, that's probably

- MySQL
- PostgreSQL
- sqlite
- generic access via ODBC

For Java, I would hope we would be able to work with anything with a
JDBC driver.

James