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 112688 - In Migrated project Unsetting Array property of ObjectArrayDataProvider does not bind the component to defaultDP
Summary: In Migrated project Unsetting Array property of ObjectArrayDataProvider does ...
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: PC All
: P2 blocker (vote)
Assignee: Matthew Bohm
Keywords: RELNOTE
Depends on:
Reported: 2007-08-13 17:46 UTC by Yousuf Haider
Modified: 2007-08-18 00:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Sample 5.5 project (3.64 MB, application/x-compressed)
2007-08-13 17:48 UTC, Yousuf Haider
diff of fix (2.67 KB, application/octet-stream)
2007-08-16 01:09 UTC, Matthew Bohm

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Haider 2007-08-13 17:46:54 UTC
Woodstock Build: Woodstock.4.1-200708081411

Steps to reproduce:

1. Download attached 5.5 project. This project has a table component that is bound to an object array data provider
whose Array property is set to an array of Person class.

2. Unset the property of OADP. Page will show source file errors:

javax.faces.FacesException: javax.el.ELException: javax.faces.el.PropertyNotFoundException:
javax.el.PropertyNotFoundException: java.lang.IllegalArgumentException: age

For NB6 projects this behavior was fixed in issue 111028. But 5.5 or 5.5.1 projects migrated in NB6 show errors.

The same error occurs if users had usnet the property in 5.5 or 5.5.1 and then migrated their project. The page would
show errors as soon as it was opened.

This is an important issue for migration since in 5.5 or 5.5.1 users could view the page without these errors (read
summary for issue 111028 for why) but once project is migrated the same page cannot be viewed in NB6.

Migrated projects should therefore exhibit the same behavior as NB6 projects.
Comment 1 Yousuf Haider 2007-08-13 17:48:17 UTC
Created attachment 46522 [details]
Sample 5.5 project
Comment 2 Matthew Bohm 2007-08-14 07:59:50 UTC
I'm not sure it has to work perfectly on a migrated project; however, the workaround I had expected to work does not
work. So I will have to investigate this further.
Comment 3 Matthew Bohm 2007-08-16 01:08:00 UTC
Fixed. See diff of fix, attached as diff-of-fix-0815-1700.txt

Checking in webui/src/designtime/com/sun/webui/jsf/component/TableRowGroupDesign;
/cvs/woodstock/webui/src/designtime/com/sun/webui/jsf/component/TableRowGroupDes,v  <--
new revision: 1.4; previous revision: 1.3
Comment 4 Matthew Bohm 2007-08-16 01:09:44 UTC
Created attachment 46709 [details]
diff of fix
Comment 5 Yousuf Haider 2007-08-18 00:21:58 UTC
Fixed and verified on 
NB Build: 200708171200
WoodStock 4.1 Build: 200708171429

There is however an issue in a customer project. If The user had bound and then unbound the array property of OADP in
5.5 then when the project is opened in NB6 the JSP still contains the relevant code and the page shows

The workaround would be to either:

1. Open the project in NB6, from the Navigator window set and unset the array property of the OADP. This will make the
OADP bound to the defaultDP and design time will be ok.

2. Bind the OADP to an array in 5.5.x and then open it in NB6 and then Unset the array property of OADP.

Since there is not much that can be done for this scenario then the particular scenario I have described in the above
paragraph could be part of a Release note and/or a migration guide.