importConstants should be allowed everywhere, not only in f:metadata

[eclipse-faces-bot]

In big and modular applications, it's to complex to import all enums via f:metadata.
Every CC or include should be able to maintain their own imports, otherwise its very hard to maintain.

[eclipse-faces-bot]

@BalusC Commented
Agreed and this is also how <o:importConstants> behaves, but the 2.3 EG decided so.

[eclipse-faces-bot]

@tandraschko Commented
I see :/ But we could talk about it again for the next version, right?

[eclipse-faces-bot]

• Issue Imported From: importConstants should be allowed everywhere, not only in f:metadata javaee/javaserverfaces-spec#1466
• Original Issue Raised By:@tandraschko
• Original Issue Assigned To: Unassigned

[tandraschko]

IMO important for JSF3

[tandraschko]

related to #1683

[volosied]

Should this be a general f:metadata revsion? Nice if the spec could be updated to handle eclipse-ee4j/mojarra#5105

[volosied]

The omnifaces documentation lists that the o:importConstants saves the objects in the request scope. Should this approach also be taken by the spec / impls?

[volosied]

Few questions:

1. Should ViewMetadata#getImportConstants change or should it still return the list of import constants?

2. Should this tag keep the same taglib uri (jakarta.faces.core) and just simply be allowed to be placed anywhere? Or should a new tag be created?

[BalusC]

Let's move to 5.0 for now. We can then take the opportunity to reconsider the f:metadata. Also related: #1849