I have narrowed down the breakage of the code completion for CDI beans.
It occurs when using the jakarta ee 9 api, when the "javax" package name
changed to the "jakarta" package name. Projects that use the "javax" API
have working code completion in JSF/JSP EL.
Creating a project (gradle or a
Thanks for the message and sorry for the issues Jason. Along with the other
suggestions that were mentioned, have you attempted to create a Maven project
using Jakarta EE?
I also had similar issues when trying Jakarta EE 9.1 (jakarta.*) namespace.
However, I was using PrimeFaces 10, which I l
Your not using the version with the new Jakarta namespace instead of the javaee
namespace are you?
Get Outlook for iOS<https://aka.ms/o0ukef>
From: Will Hartung
Sent: Thursday, December 9, 2021 3:47:38 PM
To: NetBeans Mailing List
Subject: Re: JSF CD
On Mon, Dec 6, 2021 at 12:00 PM Jason Abreu wrote:
> I have also created a sample web project using Ant and observe the same
> behavior. With the new Jakarta EE, the code assist in JSP EL ("${...}")
> and JSF EL ("#{...}") does not show any of my CDI beans, only a "No
> suggestions" message. Th
I have also created a sample web project using Ant and observe the same
behavior. With the new Jakarta EE, the code assist in JSP EL ("${...}")
and JSF EL ("#{...}") does not show any of my CDI beans, only a "No
suggestions" message. This occurs with both Ant and Gradle projects.
The code co
I'm using NetBeans 12.5 with a new Gradle 7 web project and am having
issues with code completion working within JSF EL (Jakarta JSF 3.0). I
could definitely use some assistance figuring this out.
Steps Taken:
1. Created new Gradle Web project (declared dependency for jakarta ee
9.1 api)
2.
