The JSF homepage is quite out of date, mentioning EE 7 is probably one of the least outdated parts :( I've had it on my TODO to at least somewhat update it for well over 4 months now, but haven't

Hi, The project page (see below) displays the Java EE 7 coordinates, and later on for Java EE 7 the same. I guess, the first coordinates mentioned here shall refer to Java EE 8? --

Hi, In the JAVAEE 8 Platform Specification there is Table EE.5-1 that lists component classes supporting injection. In this table the following JSF 2.3 artifacts are listed: JSF managed classes^b

PN> According to the JSF spec section 5.4.1 JSF Managed Classes and Java PN> EE Annotations, there are a bunch of JSF artifacts eligible for PN> injection. PN> On MyFaces, all these objects allow

Hello, According to the JSF spec section 5.4.1 “JSF Managed Classes and Java EE Annotations”, there are a bunch of JSF artifacts eligible for injection. On MyFaces, all these objects allow

Hello Arjan and list. Right now our total focus is completing and delivering Java EE 8 and Java SE 9, and their new capabilities, and we hope to deliver them this summer. I expect we

Hi Michael, I'd be happy to help you with your evaluation of JSF portlets. What portal product/version are you using with GlassFish? Neil

Hi, we have to handle a dataportal which is implemented with JSF. Over time, it became a huge gorilla. Since a couple of features are independent from others, I suggested to divide this

Hi, It's been a few days, so just a friendly ping ;) Are there any plans for the next spec cycle of JSF 2.3? Kind regards, Arjan Tijms

Hi, I have a rough idea, not sure how well could it work or if it would even work: On cases where there are just some methods, create a class that delegates to the deprecated module. For

There often are indeed, see for example this one: https://docs.oracle.com/javaee/7/api/javax/faces/component/ActionSource.html#getAction-- getAction returns a MethodBinding, which is the deprecated

Regardinf pre-UEL, are there already alternative methods on thosw interfaces to use UEL? I imagine that would mean a lot of duplication, unless a new interface with the same purpose could be

It's certainly effectively deprecated. Many newer features are not supported when JSP is used, which is in a way a strategy to slowly phase it out. But indeed, I love to move that one to a separate

Splitting it sounds good so people can create reduced runtimes. Btw, what about the JSP view facility? Is it already deprecated? That could be another candidate to be moved to another module

Pruning the native managed bean facility would take 2 major releases, and in Mojarra if I understood correctly it would never be truly removed. It's the RI, so after being pruned it's made optional,

Rather than prune the Managed Bean Facility (MBF) entirely, If possible, I would rather see Mojarra and MyFaces extract their MBF implementations into a separate/companion jar. That would provide for

Hi Arjan, hi Ed, personally I would prefer a kind of "continous" specification: Specify topics independently from any Java EE version and deliver the spec and RI as soon as possible.

Hi, Historically there's a gap between one spec cycle ending and the next one starting, and that gap has been widening a little over the years. What if we try to break this trend and plan for filing a

Hi, That's the other thing I'd really like to work on. I so wanted to have this in 2.3, but there's always choices to be made. As soon as the next spec cycle starts and pending spec lead and overal EG

Hi, CDI alignment is also one of my favourites. The other one would be simpler component development. Composite components are a great (but poorly documented, IMHO) feature. But even then, they are