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
- 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
- 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.
Created attachment 40246 [details]
Screenshot of the Derby module features
Created attachment 40247 [details]
Moving JavaDB/Derby to the IDE cluster - diff
Please review this change, adding the API_REVIEW_FAST keyword.
looks good to me, thanks
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.
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
> 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.
Done. nbbuild/cluster.properties rev 1.215.
> 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