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 182284 - JavaDB is not configured after adding Glassfish manually
Summary: JavaDB is not configured after adding Glassfish manually
Status: RESOLVED WORKSFORME
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Jaroslav Havlin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-18 09:50 UTC by Jiri Rechtacek
Modified: 2012-06-06 13:40 UTC (History)
3 users (show)

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 Jiri Rechtacek 2010-03-18 09:50:54 UTC
Quoted from issue 178802 - Petr Jiricka   2010-03-12 05:04:10   (-) [reply] -------

Still does not work for me in the following scenario:
1. Install NetBeans from the zip file and start with a fresh userdir
2. Go to Window -> Services and add GlassFish v3

I would expect that at this point, the JavaDB location will be initialized
using the JavaDB instance in GlassFish, the sample database will be added etc,
but it is not. To workaround this, you need to activate the Java EE features
(Java SE is not enough), after that JavaDB will be initialized.
Comment 1 Jiri Rechtacek 2010-03-18 09:59:40 UTC
Vince, could you me give a hint how to solved this scenario? It's possible to register Derby while adding Glassfish server w/o activating whole Java EE? Thanks
Comment 2 Vince Kraemer 2010-09-10 15:20:37 UTC
I have code that registers derby as part of the glassfish.javaee module.

If the derby support really is part of the ide cluster, I will move it into glassfish.common.

Sorry I did not see this earlier... or the info that derby support had moved to the ide cluster.
Comment 3 Jaroslav Havlin 2012-06-06 13:40:47 UTC
Seems to work fine in the current development build.