Bauke Scholtz

+1

Currently already implemented in EL 6.0 as per https://github.com/jakartaee/expression-language/issues/201

For the time being, you can use `items.getAttributes().put("var", "item")` instead.

> I ran into the problem earlier and configured BootsFaces to be loaded after OmniFaces. At the moment, I'm just confused if it shouldn't be before OmniFaces. OmniFaces has already...

> Or maybe as you say this has to happen in the component constructor otherwise it will happen in the wrong phase? Correct.

We're currently working on it. Until it's available, refer to the individual specifications. 1. Start at https://jakarta.ee/specifications/ 2. Pick the specification of interest, e.g. "Jakarta Faces" 3. Open the link...

I don't understand https://github.com/eclipse-ee4j/jakartaee-tutorial/pull/281/commits/48ef63c0a15be0d4b54b97a9afe8ef28ddffe024. This appears to be a unrelated change which destroys the original alphabetic ordering. Where's the ticket which discusses the new ordering? I don't remember seeing this....

Any volunteer to reassess the spec and prep a PR and/or IT?

API part of original PR is split into https://github.com/jakartaee/faces/pull/1880

API has been split from Mojarra project into Faces project. Current PR is superseded by https://github.com/jakartaee/faces/pull/1942