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 172517 - Bind to Data Provider doesn't work in visual editor of any property
Summary: Bind to Data Provider doesn't work in visual editor of any property
Status: CLOSED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P1 blocker with 1 vote (vote)
Assignee: issues@obsolete
URL: http://forums.netbeans.org/files/capt...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-17 19:15 UTC by mariano_lopez
Modified: 2011-11-28 11:37 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 mariano_lopez 2009-09-17 19:15:56 UTC
Bind to Data Provider doesn't work in visual editor of any property.

How to reproduce it:

 1.- Create a new RowSet and DataProvider in ApplicationBean1 or SessionBean1.
 2.- Create a new visual web pack page.
 3.- Insert text field in new page. For each component happens the same.
 4.- Select ellipsis button for component's text property.
 5.- Select "Use binding".
 6.- "Bind to Data Provider" tab is empty and can not bind to any DataProvider.

It works perfectly in NetBeans 6.5.1.
Comment 2 st_erdogan 2009-12-14 03:44:16 UTC
The problem is more general than stated. Refactoring of a former Java Bean or adding a new property is not noticed in binding window. 

How to produce:
1. Create a bean (for example, a business object)
2. Create a visual element (a JPanel maybe), add some textfields, spinners, etc. and bind this visual elements to the properties of the object in step 1. 
3. Now the critical part: Define new properties in the object in step 1. 
4. Go back to visual element designer. Add a new textfield and try to bind to the property.
5. The newly added property is not visible in binding window. 

I, generally, close and reopen the visual element in order to get rid of this problem, but most of the times, I have to restart the Netbeans IDE. This is a very annoying problem. Is there any workaround for the problem, by the way?
Comment 3 Jan Stola 2009-12-14 04:06:48 UTC
@st_erdogan: the problem you are refering to has nothing to do with the original bug report. The binding in visualweb is completely different from binding in Swing GUI builder. Feel free to report a new issue about your problem. I am reassigning this issue back to visualweb.
Comment 4 Jan Chalupa 2011-11-28 09:02:45 UTC
Obsolete issue. Closing.
Comment 5 Marian Mirilovic 2011-11-28 11:37:38 UTC
v/c