JSF managed beans are indeed deprecated, but not the managed bean facility defined at the platform level. If you believe they should be deprecated, the best place to start that discussion is likely the platform development mailing list. However, it helps to get more context on the use cases for managed beans first. The best source of information is likely the platform specification document.
Hope this helps.
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.
On Mar 29, 2021, at 6:05 AM, Som Lima <somplasticllc@xxxxxxxxx> wrote:
Further official documentation
_______________________________________________jersey-dev mailing listjersey-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jersey-dev
I loaded code examples in netbeans ide and it had a strike through line meaning it is deprecated.
The netbeans is the best indicator because deprecated code is programmed into the IDE.
Also it is indicated here aswell.
Why do you think jakarta.annotation.ManagedBean  has been deprecated?
I believe the following code in the jakarta jersey reference examples has been deprecated and should not be part of jakarta.
If that is the case You may to wish to look into it.
I have identified the files in question using the *.nix scripting language (A flexible therefore a powerful tool).
$ grep -RiIl '@ManagedBean'
Quick grep explanation:
-R - recursive search
-i - case-insensitive
-I - skip binary files
-l - print a simple list as output.
jersey-dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jersey-dev