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.
Registered Derby database failed to start with GlassFish V3 server Steps To Reproduce: 1. Install NB 6.7 trunk (04/14/2009) build on winXP, jdk1.6.0_13 2. Start IDE with V3 experimental option (eg. ./netbean -J-Dorg.glassfish.v3.enableExperimentalFeatures=true) 3. Select Tools > Servers > Click Add Server > Select Server for Ruby on Rails > click OK > select GlassFish V3 > click Next > check license > click Download Now... > click Finish > click Close button 4. Select Window > Services 5. Expand Servers node > right-click at GlassFish V3 server > select Start menu 6. Expand Databases node to verify BUG: The default JavaDerby database failed to start
the derby support module... which is used to start derby when the server starts is in the java cluster. So, it cannot be leveraged to start Java DB when only the jruby support is loaded/activated. the derby support depends on the 'Java Platform' module. If that dependency were broken, the derby module could move to a cluster like ide, which would allow it to be used by any of the 'bundles'... This is too big a change for 6.7... and will probably be thought of as an enhancement... not a defect. Once the derby support can be used in the Ruby and/or PHP IDE, please assign this issue back to serverplugins/gf_v3.
Reassigned to new owner.
core-main/rev/ed84ff1edba1 - moved Java DB from java cluster to ide cluster to allow using Java DB for non-java users Rest of problem is dup of issue 178802 *** This bug has been marked as a duplicate of bug 178802 ***