some more info http://java.net/jira/browse/JAVASERVERFACES-1849

Code completion fixed in web-main#a89e719b5f13

As for the false errors in editor (as described in the Mojarra issue) - CC error checking has been disabled since 7.0

Marek,

Not sure what you mean by:

As for the false errors in editor (as described in the Mojarra issue) - CC
error checking has been disabled since 7.0

I am using 7.0.1 and when if i use rendered while calling the composite component the editor does show an error.

Hmm, I was under impression the error checks for cc were disabled earlier. So it happened after 7.0.1, I'm sorry for the incorrect information. Definitively it doesn't check the cc in current dev builds.

Just for sure, it will be superb if you check it in the current dev builds or 7.1 beta.

Marek,

Does that mean that none of the attributes get checked while calling composite components? If so, that would be a shame, wouldn't it? Ideally i would like to see all the attributes being correctly checked and rendered being allowed too...

I'm afraid none of the cc sub-properties aka cc.attrs.myattr are not checked for validity. AFAIR this was dropped during a big code redesign done to 7.0. That's why I'm really confused you say it works in 7.0.1. 

I'll look at the issue tomorrow again an possibly reimplement it "a bit" so the checks for cc properties works (again).

Marek,

Sorry for the confusion:

I was taking about the error check when calling the component:

eg:

<cc:email rendered="true" value="po@po.com"/>

I was saying it would be good to keep this with error check as the only problem now was thea NB would complain about "rendered" (which is implicit but not defined in the cc's interface)

About error checking (and autocomplete) cc.attrs.xxx (inside the cc implementation) that would be great wouldn't it?

Hey,

by the way,

It would also be great if we the project explorer could tell you which jsf pages have EL errors as often renmaing/deleting a method in a backing bean breaks the jsf expression and you can't see the warning unless you log open that file again.

If yo think is doable i can open a RFE.

Integrated into 'main-golden'
Changeset: http://hg.netbeans.org/main-golden/rev/a89e719b5f13
User: Marek Fukala <mfukala@netbeans.org>
Log: #202925 - JSF 2 Composite component's implicit rendered attribute does not get picked up by the editor.

There are two more issues with very nice description complaining about the same problem:

Bug 201984 - JSF EL H:datatable - "unknown property"
Bug 193806 - "rendered" part of JSF <ui:fragment> tag seen as error

*** Bug 201984 has been marked as a duplicate of this bug. ***

*** Bug 193806 has been marked as a duplicate of this bug. ***

JSF spec 3.1.12 Render-Independent Properties: RW: id, parent, rendered, rendererType, transient; RO:  rendersChildren

It seems that "class" property is also taken into account and copied into the resulting html encosing tag.

fixed in web-main#bd35fcebffba

added some additional fixes in web-main#7fab99b711c9
- composite components attributes error checking enabled
- code completion offers the generic attributes also in composite components
- added a simple help for the generic attributes

Integrated into 'main-golden'
Changeset: http://hg.netbeans.org/main-golden/rev/bd35fcebffba
User: Marek Fukala <mfukala@netbeans.org>
Log: #202925 - default facelet component attributes "rendered" and "id" not properly handled by the editor

Integrated into 'main-golden'
Changeset: http://hg.netbeans.org/main-golden/rev/7fab99b711c9
User: Marek Fukala <mfukala@netbeans.org>
Log: #202925 - some additional fixes