db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: Is Monitor a public API? Can it be hooked to JMX?
Date Sun, 28 Nov 2004 04:56:04 GMT
Hash: SHA1

> Jeremy Boynes wrote:
>> The way we have currently embedded Derby into Geronimo is a little
>> crude and relies on a GBean (Geronimo component) starting Derby by
>> instantiating an EmbeddedDriver.
>> I started digging around looking for a better way and see that the
>> driver is really booting a set of services using the Monitor API. It
>> looks like it would be possible to integrate this directly into
>> Geronimo and have it control the server directly rather than through
>> JDBC. The big concern I have is whether this is an API intended for
>> external use?
>> Another reason for doing this is to try and integrate Derby services
>> into the management framework Geronimo exposes. It looks like it would
>> be possible to wrap some of the Derby services themselves in GBeans
>> which would then transparently expose them to management (e.g. via JMX
>> or Geronimo's console).

Well, the monitor was never intended as a public api. The public api is
defined by classes included in the javadoc created by the 'publishedapi'
target at the top level api.

I would be interested to see what you think is actually crude about the
current Geronimo integration. Integration with other application servers
such as tomcat or websphere typically use one of Derby's data source
implementations and not the embedded driver.

The management aspect sounds good, but it seems like that is exposing
management of Derby componenets through standard JMX interfaces, and
doesn't require exposing internal interfaces.

Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


View raw message