Qute: Option to disable auto generation of @Named bean ValueResolver

[gbourant]

Description

At the moment, Qute generates ValueResolver for all @Named beans. This could a bad thing for some cases in which it could potentially leak secrets to Qute templates.

Consider the following example:

public class SafeTokenProvider {
    @Produces
    @Named("safe-token-public-key")
    protected PublicKey initSafeTokenPublicKey() {
        return getPublicKey(Path.of(safeTokenPublicKeyLocation));
    }

    @Produces
    @Named("safe-token-private-key")
    protected PrivateKey initSafeTokenPrivateKey() {
        return getPrivateKey(Path.of(safeTokenPrivateKeyLocation));
    }
}

Now, we can inject the Public and Private keys in Qute templates.

Implementation ideas

No response

[quarkus-bot]

/cc @mkouba (qute)

[mkouba]

Well, the whole idea of bean names (and @Named) is to make CDI beans accessible in non-typesafe environments, such as templates and EL. So if you don't want to use the beans in such environments then do not use bean names/@Named 🤷.

In other words, I don't think this is a valid requirement.