[config-dev] CDI Integration

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[config-dev] CDI Integration

From: Scott Stark <starksm64@xxxxxxxxx>
Date: Thu, 8 Jul 2021 06:51:25 -0700
Delivered-to: config-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/config-dev/>
List-help: <mailto:config-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/config-dev>, <mailto:config-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/config-dev>, <mailto:config-dev-request@eclipse.org?subject=unsubscribe>

I just joined the list and so don't have the current message thread to respond to, so this message is in response to some of the "Proposal for CDI Integration" messages.

I do believe that use of the @Named annotation would be problematic as the CDI spec does call out that its use at injection points is not recommended.

As far as I can see, a ConfigRoot annotation still has to apply the Jakarta Injection Qualifier annotation, and so has a dependency on that api.

Beyond that api dependencies, any behavior around CDI integration would need to be validated via a config TCK. To address the dependency issues I would suggest that there be two projects in config:

- config-core : base CDI independent api and spec

- config-cdi : annotations, spec and TCK for CDI integration behavior

Prev by Date: Re: [config-dev] Proposal for CDI integration
Next by Date: [config-dev] Config Source SPI options
Previous by thread: [config-dev] Proposal for CDI integration
Next by thread: [config-dev] Config Source SPI options
Index(es):
- Date
- Thread

Breadcrumbs