Mailing-List: contact deltaspike-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltaspike-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=SM3z9C1I8ztvkNCgIltif+sLmKHtmLBbsGLAVptLZDV+MYBJbELVEleSmnMfs3jEqy6SyOKYvrLVZiLqBKqgqPBbW9ERFVRp4cL8bByupgSZeoI+7MZMK1yBcK77cB65zRKLujH+Q4r6OT2TAWukR7rnCeAs4dXlpB04Ue2Jwwk=;
Message-ID: <1339669072.96297.YahooMailNeo@web171504.mail.ir2.yahoo.com>
Date: Thu, 14 Jun 2012 11:17:52 +0100 (BST)
From: Mark Struberg <struberg@yahoo.de>
Reply-To: Mark Struberg <struberg@yahoo.de>
Subject: ConfigProperty#eager() question
To: deltaspike <deltaspike-dev@incubator.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi!=0A=0APlease take a look at ConfigProperty#eager().=0A=0AThe idea is to =
verify if every used configuration property is really available and configu=
red.=A0 =0A=0A=0AThis was initially easy to do as side effect of the Proces=
sInjectionTarget.=0A=0AThere are some restrictions with this approach as do=
cumented already: it can only verify configuration which is statically avai=
lable before the server starts. No JPA, nor any other 'dynamic' configurati=
on which gets provided by the container only at some point in time during s=
tartup or application.=0AIf enabled, it also disallows having configuration=
 which might default to null (to indicate that there is nothing configured)=
.=0A=0Awdyt?=0A=0ALieGrue,=0Astrub