This is easy to reproduce.

- Create a 6.1 project
- Drag and drop a JSF standard drop down. Shows the databinding (abc dummy data is displayed)
- Look in the outline, you have
    - Dropdown1 & dropdown1selectitems
- Go to JSP page and add a space (for insync to re-parse the page)
- Go back to designer, the data binding is gone (no dummy data is displayed)
- Look in the outline, now you have only
     - Dropdown1 

dropdown1selectitems is not resurrected.

Assigning this to insync for further evaluation.

The problem is same with "binding property" and without "binding property"

Forgot to reassign the bug.

Deva can you please have a look.

Winston, why does this happen for Standard component only. I don't think there is any special knowledge of Standard vs.
Woodstock drop down list Insync. Could this be a component bug?

Here how the binding looks like for standard drop down i.e. which is through a sub element:

                        <h:selectOneMenu id="dropdown1" style="position: absolute; left: 72px; top: 48px">
                            <f:selectItems id="dropdown1SelectItems" value="#{Page1.dropdown1DefaultItems}"/>
                        </h:selectOneMenu>

as opposed to for Woodstock:

                        <webuijsf:button id="button1" style="position: absolute; left: 96px; top: 120px" text="Button"/>

Is <f:selectItems> considered a JSF component? Could this be because we removed the binding= attribute in 6.1?

Looks like the element:

<f:selectItems id="dropdown1SelectItems" value="#{Page1.dropdown1DefaultItems}"/>

is being treated as an HtmlBean(?) due to:

    /**
     * Return the classname for a bean described by a source element iff it is our bean
     */
    public static final String getBeanClassname(Element e) {
        String ns = e.getNamespaceURI();
        :
            if (ns.equals(FacesPageUnit.URI_JSF_CORE))
                return PACKAGE + "F_" + cname;  // Faces core, use fake bean
        }
        :
    }

Sandip,
  yes, f:selectItems is  standard tag. This tag allows you to bind to an array or list of SelectItem instances.

The beanInfo for org.netbeans.modules.visualweb.xhtml.F_SelectItems is not being found.

In the 6.0 time frame the

<f:selectItems id="dropdown1SelectItems" value="#{Page1.dropdown1DefaultItems}"/>

tag looked like:

<f:selectItems binding="#{Page1.dropdown1SelectItems}" id="dropdown1SelectItems" value="#{Page1.dropdown1DefaultItems}"/>

The type of dropdown1SelectItems property was UISelectItems which did have BeanInfo

org.netbeans.modules.visualweb.faces.dt_1_2.component.UISelectItemsBeanInfo

So may be we need to copy that BeanInfo to org.netbeans.modules.visualweb.xhtml.F_SelectItemsBeanInfo

Fixed in trunk by deva, see: 8412908d4538.

ok. verified this is fixed in trunk build 1511 (Build 20080407160956).
Tested standard dropdown in 1.4 and ee5 projects. After review and incorporating 
of any feedback, this fix can be integrated in 6.1 branch. Thanks.

Re-tested updated fix in hudson trunk build 1518 (20080408015310). Verified fixed. 

Fixed in trunk.

Please integrate it into release61 asap.

Changesets for release61 :

changeset:   77176:98c49c63206a
user:        deva@netbeans.org
date:        Sun Apr 06 18:16:16 2008 -0700
summary:     Fix for #131899: getComponentClass should ignore view and subview tags

changeset:   77177:5b99453b46b5
user:        deva@netbeans.org
date:        Sun Apr 06 18:21:29 2008 -0700
summary:     Fix for #131899: change to bindMarkupBeans first to look into tag lib uri

changeset:   77178:aee518ed5824
user:        deva@netbeans.org
date:        Mon Apr 07 16:45:17 2008 -0700
summary:     Additional fix for #131899

Verified fixed in RC1 NetBeans IDE Dev (Build 200804090901)
Java: 1.6.0_10-beta; Java HotSpot(TM) Client VM 11.0-b11
System: Windows XP version 5.1