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.
|Summary:||Page needs manual refresh after opening Legacy project after component error occurs|
|Product:||obsolete||Reporter:||_ krystyna <krystyna>|
|Component:||visualweb||Assignee:||John Baker <jbaker>|
|Issue Type:||ENHANCEMENT||Exception Reporter:|
Description _ krystyna 2007-11-02 20:14:03 UTC
NB installer build 11020000 XP JDK1.6.0_03 Get component error on opening legacy project with a cannot display propertySheet1 component. Travel database gets connected ok. Pressing "Continue" button displays the designer ok, and can see propertySheet1 component OK. Not sure why the Component error is shown. This is a 551 project with dynafaces 0.0.1 complib. Attaching. 1. clean userdir, don't import any settings, 2. add compatibility kit (used force install all directories) 3. all databases disconnected 4. open DynamicDropDown project, expand node, wait for Updating Legacy scan to finish 5. double click on page1 from project node >Get red component error. Attaching screenshot. Attaching messages.log. Press continue and deploy. Appears correctly. Note that this project was from issue #105210 - used to show Missing Body Element in 5.5.1 and no longer occurs in 6.0.
Comment 4 Winston Prakash 2007-11-02 21:59:13 UTC
When page is opened, if the database is bundled then Designtime Naming Context attempt to connect the database. However, the page is not refreshed after the connection is established, that is why the page continue to display with error and a manual refresh (by pressing the continue button is required). When we press the continue button everything works fine, then why this is a p2 bug? Shouldn't it be a p3 bug if we want the page to be refreshed automatically. Also this may be a duplicate of http://www.netbeans.org/issues/show_bug.cgi?id=109163 I'm assigning this to John Baker to mark this as duplicate Assigning this to
Comment 5 John Baker 2007-11-02 22:56:07 UTC
This is related to 109163. However, if I fix 109163 then the migration would also have to be updated to support refresh May not fix for 6.0
Comment 6 _ krystyna 2007-11-02 23:46:26 UTC
I'm glad that this is non-deleterious. It's too bad users get the big bad red Component Error for a refresh issue. If "press Refresh" were included in that Component Error dialog that would help.
Comment 7 John Baker 2007-11-02 23:51:26 UTC
This may be 1) an invalid project. 2) the userdir settings from previous releases are not available on the same machine (nothing can be done about this) A dialog should open to let the user know to Resolve missing database connections. Also, for NetBeans 5.5.x project the project node will be badged, but for Creator 2 projects, the project must be closed and reopened. This has been documented in the Migration Guides From testing valid Creator2 and NB 5.5.x projects, a Component Error page hasn't opened after migrating
Comment 8 John Baker 2007-11-02 23:54:12 UTC
Also note, the project attached contains a sun-resources.xml file that was not introduced until 6.0 This project either was edited in 6.0 by adding a data source or was already migrated but used a pre-Beta release to do the migration
Comment 9 John Baker 2007-11-03 00:44:09 UTC
If components are bound to Java DB rowsets then a refresh is required.
Comment 10 John Baker 2008-01-15 23:55:03 UTC
Data bindings for pages opening with a project are resolving much better now. I think the priority can be lowered and if still needed, I won't have time to fix this for 6.1
Comment 11 John Baker 2008-01-16 00:40:53 UTC
Actually this is an enhancement since new functionality may be required.