Hi again!
On 04/24/2014 09:09 PM, Thomas Mueller wrote:
I didn't find any standard logging strategy in the h2 code base
Well, at this level there is none (I don't want to hardcode SLF4J or
use java.utils.logging). Maybe the best option is not to log.
Sure - I can remove the System.err call from the patch. One alternative
would be to use org.osgi.service.log.LogService (if *that one* is
available) - but it feels like an over-engineered solution at this
point.
But is it possible to use Class.forName instead, similar to how it's
done in org.h2.value.DataType.GEOMETRY_CLASS_NAME / GEOMETRY_CLASS,
with Class.forName()?
Are you referring to using `Utils.loadUserClass` to check if the class
is available or not (before trying to create the `OsgiDataSourceFactory`
and register it as a service)?
[snip]
Best regards //Anders
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
