This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 175062 - Missing JavaDB & jdbc:derby nodes from Databases
Summary: Missing JavaDB & jdbc:derby nodes from Databases
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: PC Windows XP x64
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-21 04:16 UTC by davisn
Modified: 2009-10-23 00:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description davisn 2009-10-21 04:16:07 UTC
-Default JavaDB and jdbc:derby://localhost:1527/sample[app on APP] sub-nodes missing from the Databases node
-This is a regression problem

Steps To Reproduce:
1. Download and install the Beta Candidate build from
http://smetiste.czech.sun.com/builds/netbeans/6.8/beta/2009-10-19_20-01-27/
2. Expand Servers node, right-click on GlassFish V3 Servers node, select "Start" menu
3. Expand the Databases node to examine
BUG:
   Both of the sub-nodes described above were missing
Comment 1 davisn 2009-10-21 04:56:37 UTC
I just found out thatthe "JavaDB and jdbc:derby://localhost:1527/sample[app on APP]" sub-nodes will only appear after
activate Web and JavaEE components. 
Comment 2 Vince Kraemer 2009-10-21 05:28:19 UTC
That functionality is dependent on the derby modules of the IDE.  Those modules are part of the 'java' cluster.  The
javaee features depend on the java cluster.  The ruby features of the IDE do not depend on the java cluster...

So, the samples database is not created or registered unless the javaee features are enabled... by design.

Since the IDE is working as designed, I am marking this issue as won't fix.
Comment 3 Vince Kraemer 2009-10-21 19:58:08 UTC
I guess this change is the root cause of this issue...

http://hg.netbeans.org/web-main/rev/2354f4681771
Comment 4 Vince Kraemer 2009-10-23 00:01:28 UTC
I misread this issue.  It is not a server plugin issue, really... The nodes in question come from the derby module...
which is not enabled by the actions described, thanks to FoD.

Since this appears to be the design... I am going to reclose this as wontfix