microbean / microbean-configuration-cdi

A CDI extension that exposes the microBean Configuration API in CDI environments.

microBean™ Configuration for CDI

The microBean™ Configuration for CDI project adapts the microBean™ Configuration API project to CDI.

microbean-configuration-cdi's Issues

Handling of empty and NULL values in ConfigurationValue#defaultValue needs fixing

See the relevant line for details. In short, trim() will return an empty string where I was expecting it to leave the string-containing-only-\0 alone.

Uptake microbean-configuration-api v0.4.2

Uptake microbean-configuration-api 0.4.2

Try to capture context somehow in which a call to configuration takes place

I have a Configuration annotation, and it is inspected all the way up the injection chain—that is, when a configuration value is requested, the extension checks to see if there is a Configuration annotation on the parameter itself, the containing method, the containing class, and so on.

But what we really need is a way somehow to investigate the calling stack for such properties/annotations. I think this will have to be a programmatic call (unless I can get complicated with a custom Thread-based scope). The general hazy ill-conceived idea is that somewhere in the call, you "mark" the current…thread, I guess, as "belonging" to a particular Configuration (fred, let's say). Then the configuration framework looks up fred.whatever-the-value-name-is.

It would be really cool if we could capture this with annotations (maybe the extension could introspect every bean in the system and somehow detect where this context was set?).

BeanManager#createInstance() is called in ProcessInjectionPoint observer

In Weld 3.0.0.CR2, this is not a problem. In Weld 3.0.0.Final, this throws an exception. We need to move this call somehow to AfterDeploymentValidation-time.

Specification reference: http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#beanmanager

Eliminate the unnecessary creation of a Configurations instance

The extension accidentally creates two instances of Configurations, which is not necessarily a lightweight operation.