>
> Alternatively, we could treat all these as properties, distinguished only
> by name, so that connection pool properties are always named "pool.*" and
> any property name that doesn't start with "pool." is considered a JDBC
> driver property. Given the way these properties are used, that doesn't
> feel like the right solution to me, but admittedly it will certainly work
> and it's not "terrible".
That would work. But it doesnt seem the right way of implementation to me.
Even if take this approach, CLI and GUI should be able to distinguish these
two sets of properties. Overall, it will be simpler to modify the DTD to
allow
these two sets properties.
- Binod.