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 117711

Summary:	[60cat] Unable to change the ID property in the JSP code
Product:	obsolete	Reporter:	racx <racx>
Component:	visualweb	Assignee:	_ sandipchitale <sandipchitale>
Status:	STARTED ---
Severity:	blocker
Priority:	P3
Version:	6.x
Hardware:	PC
OS:	Windows XP
Issue Type:	ENHANCEMENT	Exception Reporter:

Description racx 2007-10-03 23:16:41 UTC

[ BUILD # : 200710020000 ]
[ JDK VERSION : 1.6.0_02 ]

To reproduce:

1- In the visual editor, drop 1 hidden field, then through the JSP code, change the ID name for that field. 

2- Switch back to Visual view, and drop another hidden field, then enter the JSP code again, the ID of the last hidden 
field is switched back to hiddenField1 (Default name) instead of the new ID we named!

Note: This is happening as well with the rest of the components but the hidden field's properties doesn't appear in 
the IDE componenty property where we can change the ID.

Comment 1 racx 2007-10-04 04:49:00 UTC

I noticed that the IDE is obliging us to have the name of the bounded variable the same as the ID... Is this a correct 
behaviour? As far as I know the component can have an ID with a name different then the name of the variable bounded 
to. There is no obligation to have the same naming.

Thanks,

Rachad

Comment 2 Lark Fitzgerald 2007-10-04 19:37:13 UTC

I can reproduce this. I've reassigned this to insync/sandip so he can explain, but I believe it is working as expected 
as two way synchronization has never been 100% supported.  To change the ide, select the component in the ouline 
window to bring up properties and change it there.

Comment 3 _ sandipchitale 2007-10-27 17:09:29 UTC

Modifying the id property in JSP code was/is not supported. Also restriction on binding names will be fixed in future
release.

Comment 4 racx 2007-10-27 20:32:13 UTC

Great! I think it is amissing functionality.

Comment 5 _ sandipchitale 2008-03-26 16:32:58 UTC

We may consider this in the future release.

The requirement for having a binding attribute for each component has now been relaxed. So the change of ID property may
work anyway in cases when there is no binding attribute.