[
https://issues.apache.org/jira/browse/NETBEANS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16955295#comment-16955295
]
Pablo Fernández Peña commented on NETBEANS-84:
----------------------------------------------
Hi [~Juneau001], again! :)
Activating the CDI alignment of JSF 2.3 through the *@FacesConfig* annotation
(_very important_) it activates the CDI-Injection of JSF Owned Types in Java
code, and the CDI-EL Resolver for that types in Facelets. Regarding these in
NetBeans it happens:
1) All CDI-EL Resolved types are properly recognized by NetBeans when editing
the facelets (being cautious that for some types and its qualifier, the names
are pretty different, e.g. in Java code "@Inject @RequestParameterValuesMap
Map<String, String[]> requestParameterValuesMap;" is in EL "#\{paramValues}"),
but not for one; "#\{externalContext}" is not recognized, although not displays
any error (so it is not critical) it not code assist the user so I think it is
not recognized:
!image-2019-10-19-18-11-36-478.png|width=999,height=481!
[^newInJSF23.xhtml]
2) Regarding the CDI-Injection of JSF Owned Types in Java code, none of the
types are recognized as CDI available injection points, it is displayed as a
warning so it is not critical:
!image-2019-10-19-18-17-10-545.png|width=999,height=480!
[^NewInJSF23.java]
As you see both issues are not critical and also involve CDI, but I think they
are principally JSF 2.3 related issues that NetBeans must support to be "JSF
2.3 compliant".
Regards, Pablo.
> Support for JSF 2.3
> -------------------
>
> Key: NETBEANS-84
> URL: https://issues.apache.org/jira/browse/NETBEANS-84
> Project: NetBeans
> Issue Type: Improvement
> Components: javaee - JSF
> Affects Versions: 8.2, 9.0, Next
> Reporter: Philip Durbin
> Assignee: Josh Juneau
> Priority: Critical
> Labels: pull-request-available
> Fix For: 11.3
>
> Attachments: NewInJSF23.java, NewInJSF23.java,
> image-2019-10-19-17-33-34-341.png, image-2019-10-19-17-34-47-683.png,
> image-2019-10-19-18-11-36-478.png, image-2019-10-19-18-17-10-545.png,
> netbeans-red-jsf2.3.png, newInJSF23.xhtml, newInJSF23.xhtml
>
> Time Spent: 768h 50m
> Remaining Estimate: 0h
>
> One thing that struck me while attending Ed Burns' JSF talk[1] about JSF 2.3
> at JavaOne 2017 was a comment he made that autocompletion isn't working in
> Netbeans for JSF 2.3 features. I would describe this as NetBeans 8.2 showing
> "angry red" for components it doesn't understand, such as f:validateWholeBean.
> As in the attached screenshot, an example error is "The component library Jsf
> Core does not contain component validateWholeBean".
> Here's the code from the screenshot:
> https://github.com/javaee/glassfish-samples/blob/4b3a37500a256bb7d94e2abe273503c9fb017c6b/ws/javaee8/jsf/ee8additions/src/main/webapp/validateWholeBean.xhtml
> In the past, NetBeans releases were coordinated with Java EE releases. When
> Java EE 8 came out, I expected that NetBeans 9 would come out and support JSF
> 2.3. When we onboard new developers, I would rather not say to them, "It's ok
> to see angry red like this in NetBeans."
> Incidentally, during Ed's talk I asked if he knew if JSF 2.3 is supported by
> IntelliJ or Eclipse and he wasn't aware if they support it or not.
> !netbeans-red-jsf2.3.png|thumbnail!
> !https://issues.apache.org/jira/secure/attachment/12891266/netbeans-red-jsf2.3.png|height=300,width=444!
> [1] Contemporary Java Web Applications with JSF 2.3 -
> https://www.youtube.com/watch?v=yshXLB_HdhU
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
