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.
Reproduce: New Project, label on Page, place Object (not String or primitive) in SessionBean1, try to bind label to object (or deeper): use binding -> Bind to an Object -> SessionBean1 -> BINDING DOES NOT SHOW UP Remark: It works in 6.0. No workaround like build, close, reopen.
The information shown in the binding dialogs are obtained from the DesignContext from insync. Pass it on to insync folks for further evaluation.
I think only the first level of objects + it's props comes from Insync. I think rest of it is based on reflection. In any case this may be an issue of not having compiled the project to make sure the class file for "that" object (e.g. Person.java with properties 'String name' and 'int age' in project's source tree) is available. Please compile the project and then try it.
No Bug:-) Sorry, problem was on my side: Likely some earlier dev installation was not successful. Somehow the VisualJSF Plugin was not activated. I removed the user/.netbeans/dev -> everything works fine.
Testcase to reproduce (zipped NBproject attached): - jdk 1.6.0_05 - NB 6.1 DEV 200803140008 - external library ExternalLibrary.jar placed in projects lib directory. - has a Class Data - hat a private String text property with public getter and setter - SessionBean1 has a private Data property with public getter and setters - Two Pages - Page 1 - label without value binding - Page 2 - label with value binding: text="#{SessionBean1.data.text}" Behavior on NB 6.0.1: - on Page 1 it is possible to set the binding using the wizzard on the text property of the label - Page 2 is rendered at design time Behavior on NB 6.1: - on Page 1 the property data does not show up in the wizzard - Page 2 is not rendered at design time - instead exception
Created attachment 58398 [details] VWP project reproducing issue
Ah!, I see you are using external library jar. Yes, this is a known issue and tracked in another p1 bug. Marking this bug as duplicate of that bug *** This issue has been marked as a duplicate of 130231 ***