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 115729 - DesignTime context not created properly if multiple projects opened
Summary: DesignTime context not created properly if multiple projects opened
Status: VERIFIED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: John Baker
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2007-09-17 16:56 UTC by _ alexpetrov
Modified: 2007-09-18 12:49 UTC (History)
1 user (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 _ alexpetrov 2007-09-17 16:56:54 UTC
Product Version: NetBeans IDE Dev (Build 200709150000) 
Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b02 
System: Windows XP version 5.1 running on x86

1. Connect to Java DB "Travel"
2. Create new VWP project (Glassfish V2, JavaEE 5, Visual Web JavaServer Faces)
3. DnD JSF component "Drop Down List" on Designer, DnD DB table "Person" on it.

Result:
- name of new DataProvider's tree node in the window Navigator will be "cachedRowSetDataProvider1" 
  instead of "personDataProvider"

This bug was found by automated tests, related to DB area.

May be this bug happens due to the bug http://www.netbeans.org/issues/show_bug.cgi?id=115685.
Comment 1 John Baker 2007-09-17 18:40:26 UTC
If multiple projects opened then the design-time context is not created properly
Comment 2 John Baker 2007-09-17 18:48:17 UTC
This was caused by a fix for 114703.
As suggested by insync
Comment 3 _ jimdavidson 2007-09-17 19:26:29 UTC
I tried following the steps outlined in desc1, and everything worked for me.  I was using a developer build from this
morning.  It looks like the latest fixes took care of this.

There may be a separate issue regarding multiple open projects.
Comment 4 John Baker 2007-09-17 21:26:56 UTC
Apparently, in one circumstance, when dropping a component on the page, the lookup considers the active
component to be the Services window, not the Designer multiview.

Use case works:
1) Create a new project
2) Create another new project
3) Click on the Page1 tab for the first project then either click on the Designer or drag and drop a component
4) Then drag and drop a database table

Active top component is the Multiview

This works

Use case fails:
1) Create a new project
2) Create another new project
3) Click on the Page1 tab for the first project then drag and drop a database table

Active component is the Explorer (or Services tab)

The extra click on the Designer sets it as the active TopComponent.

Something may have changed in the Window manager or Designer.  I do have a workaround for this.

I'll run the database automated tests before integrating.
Comment 5 John Baker 2007-09-17 22:24:15 UTC
Fix

Checking in visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/datasource/CurrentProject.java;
/cvs/visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/datasource/CurrentProject.java,v 
<--  CurrentProject.java
new revision: 1.20; previous revision: 1.19
done
Comment 6 _ alexpetrov 2007-09-18 12:49:38 UTC
Verified on

Product Version: NetBeans IDE Dev (Build 200709180000) 
Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b02 
System: Windows XP version 5.1 running on x86

The 1st scenario is not reproduced.