deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Struberg <strub...@yahoo.de>
Subject ConfigProperty#eager() question
Date Thu, 14 Jun 2012 10:17:52 GMT
Hi!

Please take a look at ConfigProperty#eager().

The idea is to verify if every used configuration property is really available and configured. 



This was initially easy to do as side effect of the ProcessInjectionTarget.

There are some restrictions with this approach as documented already: it can only verify configuration
which is statically available before the server starts. No JPA, nor any other 'dynamic' configuration
which gets provided by the container only at some point in time during startup or application.
If enabled, it also disallows having configuration which might default to null (to indicate
that there is nothing configured).

wdyt?

LieGrue,
strub

Mime
View raw message