Bug 99655 - Move the Derby/JavaDB module to the IDE cluster
Move the Derby/JavaDB module to the IDE cluster
Status: RESOLVED FIXED
Product: db
Classification: Unclassified
Component: Derby
6.x
All All
: P2 (vote)
: 6.x
Assigned To: apireviews
: API_REVIEW_FAST
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-02 10:12 UTC by Petr Jiricka
Modified: 2007-04-08 10:32 UTC (History)
5 users (show)

See Also:
Issue Type: TASK
:


Attachments
Screenshot of the Derby module features (74.81 KB, image/png)
2007-04-02 10:19 UTC, Petr Jiricka
Details
Moving JavaDB/Derby to the IDE cluster - diff (8.79 KB, text/plain)
2007-04-02 10:22 UTC, Petr Jiricka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2007-04-02 10:12:32 UTC
Currently, the Derby/JavaDB module is a part of the enterprise4 cluster, which
means that it is not available when using the IDE without the Java EE features.
However, this module is useful other scenarios as well, e.g. with Matisse data
binding, or in Rails development, as it provides out of box experience for these
scenarios. So, I propose moving it to the 'ide' cluster. 

The Derby/JavaDB module does not include the Derby engine itself, only the
integration UI. The size of the module (nbm file) is 120kB.

The module provides the following features:
- Menu items for starting/stopping the database engine, and for creating a new
database.
- Automatically detecting and registering the Derby engine bundled with JDK 6.
When not running on JDK 6, there are several other ways to get the engine: by
registering Sun Appserver (which bundles Derby), downloading it from Apache and
providing the install location in advanced options, or getting it from the
update center. 
- Registering the Derby/JavaDB JDBC drivers: embedded and "net".
- Contains a sample database (with tables Product/Customer/Manufacturer/...)

I am attaching a screenshot showing the module features.

I am also attaching a diff of the proposed change.
Comment 1 Petr Jiricka 2007-04-02 10:19:30 UTC
Created attachment 40246 [details]
Screenshot of the Derby module features
Comment 2 Petr Jiricka 2007-04-02 10:22:15 UTC
Created attachment 40247 [details]
Moving JavaDB/Derby to the IDE cluster - diff
Comment 3 Petr Jiricka 2007-04-02 10:28:55 UTC
Please review this change, adding the API_REVIEW_FAST keyword.
Comment 4 Pavel Buzek 2007-04-02 10:54:28 UTC
looks good to me, thanks
Comment 5 Torbjorn Norbye 2007-04-03 01:15:52 UTC
I've been trying to use Java DB with Rails and have run into some problems; Rails wants to have -multiple- 
databases (one for development, one for testing, and possibly one for production). You need both 
development and testing database connections; Rails unit testing will use the test database for example. 
Migration targets run these tests automatically.

It looks like the Java DB support in NetBeans assumes that a Java DB connection is a singleton (look at the 
settings in the Advanced panel).  I've had some difficulties being able to start multiple databases.
Comment 6 David Vancouvering 2007-04-03 01:19:17 UTC
I think that the settings window is confusing.  What you are setting is the
directory that contains Java DB database*s*, not the directory for a single
database.  But that's not clear from the properties window.  But really, NB does
support multiple Java DB database instances (I'm not sure how well this is
tested or how easy it is (I've logged some bugs in that regard), but I've been
able to get it to work
Comment 7 Andrei Badea 2007-04-03 09:31:15 UTC
> But that's not clear from the properties window.

The description of the Database Location field, which is visible when you click
on the field, says this is the directory where the database*s* are located, and
goes on to say it will be used as the derby.system.home property. Do you have
any ideas on how to make message less confusing?

> I've had some difficulties being able to start multiple databases.

Tor, please file those as separate issues and give some details on what you were
trying to do.

All , please let's move discussions not related to this API change somewhere
else, e.g. dev@db.
Comment 8 Petr Jiricka 2007-04-06 16:11:21 UTC
Done. nbbuild/cluster.properties rev 1.215.
Comment 9 Torbjorn Norbye 2007-04-06 16:19:00 UTC
> Do you have any ideas on how to make message less confusing?

To me, "Database Storage" would be much more clear (e.g. you'd have Database Installation and Database 
Storage).


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