Mailing-List: contact deltaspike-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltaspike-dev@incubator.apache.org
Received-SPF: neutral (nike.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=U25OFln+xz1lpdJFoF02S9Et4sU985K0Sf3aROscfMq+K0Iunxlez9BDkbFX7ZOOzGraiRq/CVRlbhfapFvdDACMJeZdgWGZT7fUJ6/u5o2ujTyHMTMT03OaSA8s5JQ06YDBrkjosXK3KmR9IixJh8PB1UbAx+tVEmbrqJdAtUc=;
Message-ID: <1340864789.51324.YahooMailNeo@web171502.mail.ir2.yahoo.com>
Date: Thu, 28 Jun 2012 07:26:29 +0100 (BST)
From: Mark Struberg <struberg@yahoo.de>
Reply-To: Mark Struberg <struberg@yahoo.de>
Subject: MessageBuilder take3
To: deltaspike <deltaspike-dev@incubator.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

... and a take 4 will follow I'm sure :)=0A=0AHi!=0A=0AThe MessageBuilder i=
s now working a bit better, but I'm still not satisfied.=0A=0AWhat I change=
d so far:=A0=0A=0AHow it works:=0A=0AThere are 2 big areas in the game=0A=
=0A1.) the MessageContext. This contains the core messaging functionality, =
a fluent API and a configuration section.=0A=0A=0A=0A2.) the typesafe @Mess=
ageBundle + MessageBundleInvocationHandler. There have been lot's of code i=
nside the invocation handler which logically should rather be handled in th=
e MessageContext. I now moved the whole ResourceBundle handling to the Mess=
ageContext for example. Prior to that it had not been possible to create a =
messagebundle text with the fluent api. I'm still not 100% happy with some =
parts but the functionality works now at least.=0A=0A=0A=0AIt's now also a =
bit easier to change the default behaviour of the MessageContext.=0AThe con=
figuration consists off 3 parts=0A=0Aa.) the LocaleResolver (resolves en_US=
, de_AT, ...). We do not inject a final Locale but only the Resolver, becau=
se in e.g. JSF this information can be taken from the ViewRoot, the logged =
in user, etc...=0A=0Ab.) the MessageInterpolator. The default one now uses =
the String.format which allows lots of tweaks. If someone used the java.tex=
t.MessageFormat in his project in the past, then he can simply change this =
now.=0A=0Ac.) the MessageResolver. This is the location where messages will=
 be taken from the ResourceBundle. I needed to add an 'initialize' method w=
hich is slightly 'out of tune' from my gut feeling. Maybe we should give it=
 a way to resolve the other configurations from the MessageContext? Please =
review!=0A=0AI'll write another mail about the @DefaultConfiguration...=0A=
=0ALieGrue,=0Astrub=0A