Bug 68524 - API for setting the location of the Derby database
API for setting the location of the Derby database
Status: NEW
Product: db
Classification: Unclassified
Component: Derby
5.x
All All
: P2 (vote)
: TBD
Assigned To: Libor Fischmeistr
issues@db
: API, API_REVIEW_FAST
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-11-11 09:59 UTC by Andrei Badea
Modified: 2013-08-01 12:53 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments
Diff with changes (1.36 KB, text/plain)
2005-11-11 10:03 UTC, Andrei Badea
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrei Badea 2005-11-11 09:59:31 UTC
I would like to ask for a review of the API for setting the location of the
Derby database.

NetBeans 5.0 we will provide out-of-the-box support for the Derby database like
starting/stopping the server, registering the JDBC drivers and creating new
databases. These features will be provided by the Derby support module in
db/derby. However, this module will not bundle the Derby database itself.
Instead, the Derby database will be provided by the module in db/derby/bundled
and by the Sun Java System Application Server 8.2. Therefore an API is needed
for the Derby bundle module and the appserver plugin module to provide the
location of the Derby database.

The intended API category is friend and will be provided by the Derby support
module. The providing module and the client modules will all be in the
enterprise cluster.

The API consists of a class with two methods (see the attached diff). The
setDerbyLocation() method is used to set the location and getDerbyLocation() is
used to retrieve it. The getter is needed so that the API client can detect that
the location has already been set and not do it again.
Comment 1 Andrei Badea 2005-11-11 10:03:54 UTC
Created attachment 26854 [details]
Diff with changes
Comment 2 Jiri Rechtacek 2009-10-16 14:09:43 UTC
Reassigned to new owner.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo