Berin,
> AvalonDB isn't a component, but a server or application--much the
> same way JAMES is. As such, it doesn't really fit the charter of
> what we do.
I stand corrected. I thought that AvalonDB was a reusable a JDBC database
component that, for example, James could use. As it is, I am looking to
embed HypersonicSQL, using the Avalon supplied code, for that purpose.
I do wonder whether or not Paul & Co ought to see whether or not it might
make sense to merge with axion. Why do things redundantly if there is the
possibility of collaborating?
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
