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 113243 - Migrating 5.5 settings may corrupt 6.0 database configuration
Summary: Migrating 5.5 settings may corrupt 6.0 database configuration
Status: RESOLVED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 6.x
Hardware: PC All
: P3 blocker (vote)
Assignee: John Baker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-20 19:27 UTC by John Baker
Modified: 2007-08-30 04:03 UTC (History)
2 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 John Baker 2007-08-20 19:27:16 UTC
from http://www.nabble.com/forum/ViewPost.jtp?post=12199034&framed=y

User was unable to connect to the sample databases.  It appears this was due to migrating 5.5 settings, although
no bug has been reported yet.

user also states:

"However, several days ago I was able to use the Java EE 5 SDK's JDK (1.6.?)and GlassFish V2 b58 to build and deploy the
WebJpa sample app. I've decided to purge my system of all NB-related folders and nbi Windows registry entries, and go
back to NetBeans 5.5. I'm looking forward to the 6.0 final release but will install on a different machine. I think the
prompt "Import NetBeans 5.5 settings?" during NB 6.0M10 installation should briefly explain the consequences for 6.0's
configuration. I suppose developers who have worked with 5.5 should know what to expect."
Comment 1 John Baker 2007-08-20 19:35:07 UTC
this makes a good test case

1) Install NetBeans 5.5 and create a sample application that connects to Java DB
2) Exit 5.5 and start 6.0 (make sure to click Yes to migrate 5.5 settings)
3) Confirm that the Java DB connections are still valid (view data on each)
4) Open the sample application and execute
Comment 2 Yousuf Haider 2007-08-20 20:46:16 UTC
I was not able to reproduce this issue.

Here is what I did:

1. Installed 5.5. Created a VW application using 5.5 which uses datasources sample and travel.
2. Closed 5.5 and opened NB6. Clicked Yes to migrate settings.
3. I was able to connect to both databases and view data as well without any problems.


One thing to note was that under the 

Databases->
          Drivers 

node in services tab the Embedded and Network drivers for JavaDB were actually drivers located in the appserver
installed for 5.5 and not the ones that come with Bundled Glassfish in NB6. This could have been a reason why the
customer was having the problem. 

Also I created a couple of projects that used the sample databases and was able to deploy without facing any issues.
Comment 3 John Baker 2007-08-30 04:00:45 UTC
The user experience has been much improved.

After opening a NetBeans 5.5 project, expand the project node.  A "Update Legacy Project" progress bar
will open at the bottom. After the progress bar has completed and dispenses, database drivers and connections get
registered and the project is updated.
Comment 4 John Baker 2007-08-30 04:03:01 UTC
Also, if database connections needed by the project were also not available in 5.5 then an alert dialog opens
to alert the user to resolve the database connections through the project node.
The project node will be badged and display name, red.  Right-click on the project node and choose Resolve Database
Problem...  Dialogs open to help guide the user to restore the necessary drivers and connections