deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Porter <lightguard...@gmail.com>
Subject Re: [DISCUSS] [DELTASPIKE-27] CodiConfig
Date Fri, 23 Dec 2011 03:37:37 GMT
+1

Needs a better name though :P

On Thu, Dec 22, 2011 at 04:03, Christian Kaltepoth
<christian@kaltepoth.de>wrote:

> +1
>
> I really like this way of configuration. It should definitively be
> part of DeltaSpike.
>
> Christian
>
>
> 2011/12/22 Mark Struberg <struberg@yahoo.de>:
> > +1
> >
> >
> > Please note that CodiConfig doesn't contain any logic! It's really just
> a marker interface to mark our SPI classes which are to be
> implemented/overwritten in a customer project to configure the provided
> functionality.
> >
> > LieGrue,
> > strub
> >
> >
> >
> > ----- Original Message -----
> >> From: Gerhard Petracek <gerhard.petracek@gmail.com>
> >> To: deltaspike-dev@incubator.apache.org
> >> Cc:
> >> Sent: Wednesday, December 21, 2011 9:41 PM
> >> Subject: Re: [DISCUSS] [DELTASPIKE-27] CodiConfig
> >>
> >> +1
> >>
> >> regards,
> >> gerhard
> >>
> >>
> >>
> >> 2011/12/21 Gerhard Petracek <gerhard.petracek@gmail.com>
> >>
> >>>  hi @ all,
> >>>
> >>>  fyi: please check [1] before you answer.
> >>>
> >>>  [2] shows how to provide custom config-values in a type-safe manner.
> >>>
> >>>  the basic concept:
> >>>  CodiConfig itself is just a marker interface to find all config
> classes
> >>>  easily. a config class is a simple application scoped cdi-bean with
> getter
> >>>  methods.
> >>>  a config can be accessed easily via std. cdi injection. users see the
> >>>  default-values as well as custom configured values easily.
> >>>  to provide custom values, users just have to extend the config class,
> >>>  annotate it with @Specializes and to override the corresponding
> method.
> >>>  furthermore, it's possible to provide config modules which allow to
> use
> >>>  different kinds of config formats like xml files, property files,...
> >>>  (due to the @Specializes bug in weld, we had to introduce a
> workaround.
> >>>  however, since weld v1.1.4 it's fixed and so we don't need the
> >> workarounds
> >>>  we introduced for it and it's as simple as the previous description.)
> >>>
> >>>  please send
> >>>  +1, +0 or -1 because...
> >>>  for the basic idea as well as the basic concept.
> >>>  if there are >basic< objections, please also add them to [3]
> >>>
> >>>  regards,
> >>>  gerhard
> >>>
> >>>  [1] http://markmail.org/message/7yefspfuvtz4jvmp
> >>>  [2]
> https://cwiki.apache.org/confluence/display/EXTCDI/JSF+Config+and+SPI
> >>>  [3]
> >>>
> https://cwiki.apache.org/confluence/display/DeltaSpike/SE+Feature+Ranking
> >>>
> >>
>
>
>
> --
> Christian Kaltepoth
> Blog: http://chkal.blogspot.com/
> Twitter: http://twitter.com/chkal
>



-- 
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message