<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:277033800;
mso-list-type:hybrid;
mso-list-template-ids:344065496 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Hi James<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I follow also Antoine and Werner that it makes no sense to just add an annotation due to the reason, that adding such an annotation it would requires also to define the exact functionality. This has severe downsides,
or basically is not possible within the CDI scope since:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">there are many different views, what such an annotation should do<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">if you interpret it widely (and flexible, which makes sense looking at the variety of possible use cases/requirements), you will end up in a complete additional kind of configuration “sub-spec”,which
would bloat the CDI spec. This is also not necessary, since we can do everything we want without any additions to CDI. Even configuring CDI is no issues, since the SPI (extensions) are so incredibly flexible ;)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">if you define the semantics more constraint, e.g. as suggested (system and env properties), it would render the annotation quite useless, for a lot of legit use cases can not be covered. And even with
these env / sys properties many questions are still open (like overriding order, overriding policies to mentions some), which are definitively out of scope for CDI as spec.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Looking at Apache Tamaya (<a href="http://tamaya.incubator.apache.org">http://tamaya.incubator.apache.org</a> ), where I together with some other guys (including Mark and Gerhard from Deltaspike) are trying to
define a common, minimalistic, but extensible API/SPI, I think we have all the ingredients for a future and unified approach for this topic. We can with the couple of API artifacts we have defined (e.g. see
<a href="https://github.com/apache/incubator-tamaya/blob/master/docs/API.adoc">https://github.com/apache/incubator-tamaya/blob/master/docs/API.adoc</a> ), cover everything, what Deltaspike can do for you today, but also the most complex requirements I am aware
of, basically fit into this simple approach there. So I would like to encourage you to join our Apache Project and help to drive Apache Tamaya, so we can increase adoption quickly and then hopefully get enough momentum to make it a JSR.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Cheers,<br>
Anatole<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">---------- Forwarded message ---------<br>
From: Werner Keil <<a href="mailto:werner.keil@gmail.com">werner.keil@gmail.com</a>><br>
Date: Fr., 6. Feb. 2015 um 11:22<br>
Subject: Re: [cdi-dev] [JBoss JIRA] (CDI-504) have a standard CDI annotation like<br>
To: cdi-dev <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">James,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I agree with Antoine as IMHO this would exceed the scope of core CDI a bit.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">There was a discussion by Anatole Tresch (also member of this EG) about creating a dedicated Configuration JSR (modeled among others also a lot after what DeltaSpike does) but so far JCP officials first and foremost Oracle saw either no
need or no resources to do this.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Apache Tamaya was a logical result. If that could become a blue-print or initial contribution of a future JSR, let's see, maybe for EE 9. It uses other Apache projects like DeltaSpike where applicable, but may also define such annotations
and types of its own, so I suggest you also share your ideas on a Tamaya mailing list or JIRA:
<a href="http://tamaya.incubator.apache.org/index.html" target="_blank">http://tamaya.incubator.apache.org/index.html</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">On Fri, Feb 6, 2015 at 11:02 AM, <<a href="mailto:cdi-dev-request@lists.jboss.org" target="_blank">cdi-dev-request@lists.jboss.org</a>> wrote:<o:p></o:p></p>
</div>
<div>
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">Send cdi-dev mailing list submissions to<br>
<a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">
https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:cdi-dev-request@lists.jboss.org" target="_blank">cdi-dev-request@lists.jboss.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:cdi-dev-owner@lists.jboss.org" target="_blank">cdi-dev-owner@lists.jboss.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of cdi-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. [JBoss JIRA] (CDI-504) have a standard CDI annotation like<br>
@ConfigProperty from deltapsike (James Strachan (JIRA))<br>
2. [JBoss JIRA] (CDI-504) have a standard CDI annotation like<br>
@ConfigProperty from deltapsike (Martin Kouba (JIRA))<br>
3. [JBoss JIRA] (CDI-504) have a standard CDI annotation like<br>
@ConfigProperty from deltapsike (John Ament (JIRA))<br>
4. [JBoss JIRA] (CDI-504) have a standard CDI annotation like<br>
@ConfigProperty from deltapsike (James Strachan (JIRA))<br>
5. [JBoss JIRA] (CDI-504) have a standard CDI annotation like<br>
@ConfigProperty from deltapsike (James Strachan (JIRA))<br>
6. [JBoss JIRA] (CDI-504) have a standard CDI annotation like<br>
@ConfigProperty from deltapsike (James Strachan (JIRA))<br>
7. [JBoss JIRA] (CDI-504) have a standard CDI annotation like<br>
@ConfigProperty from deltapsike (Antoine Sabot-Durand (JIRA))<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 5 Feb 2015 05:01:49 -0500 (EST)<br>
From: "James Strachan (JIRA)" <<a href="mailto:issues@jboss.org" target="_blank">issues@jboss.org</a>><br>
Subject: [cdi-dev] [JBoss JIRA] (CDI-504) have a standard CDI<br>
annotation like @ConfigProperty from deltapsike<br>
To: <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
Message-ID:<br>
<<a href="mailto:JIRA.12562481.1423130482000.44616.1423130509034@Atlassian.JIRA">JIRA.12562481.1423130482000.44616.1423130509034@Atlassian.JIRA</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
James Strachan created CDI-504:<br>
----------------------------------<br>
<br>
Summary: have a standard CDI annotation like @ConfigProperty from deltapsike<br>
Key: CDI-504<br>
URL: <a href="https://issues.jboss.org/browse/CDI-504" target="_blank">
https://issues.jboss.org/browse/CDI-504</a><br>
Project: CDI Specification Issues<br>
Issue Type: Feature Request<br>
Reporter: James Strachan<br>
<br>
<br>
Docker and containerisation is the new hotness; in the docker world images are static and the main way of injecting configuration is via environment variables - so that the same image can be reused but configured at run time with different configuration values.
(Changing configuration files requires either different images to be created or using custom volumes which is less ideal in a containerized world).<br>
<br>
So IMHO CDI should provide a simple, natural way to allow environment variables (or system properties) to be easily injected via CDI.<br>
<br>
Delta Spike as a @ConfigProperty annotation which works very nicely<br>
<a href="http://deltaspike.apache.org/documentation/configuration.html" target="_blank">http://deltaspike.apache.org/documentation/configuration.html</a><br>
<br>
you can specify a name, default value and use it on an @Inject to provide a value from env vars, system properties or provide a default.<br>
<br>
Given how core and useful this is - it feels like it should be part of the CDI specification; its one simple annotation.<br>
<br>
Currently deltaspike provides a way to configure different sources and whatnot which is cool; I'd be happy if CDI just had a simpler annotation which was only bound to env vars / system properties.<br>
<br>
e.g. @EnvironmentProperty(name = "envvar", deafultValue="cheese")<br>
<br>
There could be debate on whether env vars or system properties should win if the same name is used for both; in a dockerized world I'd prefer env vars to win but folks can always tinker with their run command to make sure they pass in env vars as system properties
to work around this I guess.<br>
<br>
<br>
<br>
--<br>
This message was sent by Atlassian JIRA<br>
(v6.3.11#6341)<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 5 Feb 2015 10:30:50 -0500 (EST)<br>
From: "Martin Kouba (JIRA)" <<a href="mailto:issues@jboss.org" target="_blank">issues@jboss.org</a>><br>
Subject: [cdi-dev] [JBoss JIRA] (CDI-504) have a standard CDI<br>
annotation like @ConfigProperty from deltapsike<br>
To: <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
Message-ID:<br>
<<a href="mailto:JIRA.12562481.1423130482000.45712.1423150250888@Atlassian.JIRA">JIRA.12562481.1423130482000.45712.1423150250888@Atlassian.JIRA</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
<br>
[ <a href="https://issues.jboss.org/browse/CDI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038005#comment-13038005" target="_blank">
https://issues.jboss.org/browse/CDI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038005#comment-13038005</a> ]<br>
<br>
Martin Kouba commented on CDI-504:<br>
----------------------------------<br>
<br>
What's wrong with {{java.lang.System.getProperty()}} and {{java.lang.System.getenv()}}? I mean the main advantage of DS Configuration is IMO the resolution mechanism and the ability to extend the set of {{ConfigSource}} s. If you only need system properties
and env variables a simple producer method and qualifier (or even a simple util method) would be sufficient. In other words I see no reason to standardize this.<br>
<br>
> have a standard CDI annotation like @ConfigProperty from deltapsike<br>
> -------------------------------------------------------------------<br>
><br>
> Key: CDI-504<br>
> URL: <a href="https://issues.jboss.org/browse/CDI-504" target="_blank">
https://issues.jboss.org/browse/CDI-504</a><br>
> Project: CDI Specification Issues<br>
> Issue Type: Feature Request<br>
> Reporter: James Strachan<br>
><br>
> Docker and containerisation is the new hotness; in the docker world images are static and the main way of injecting configuration is via environment variables - so that the same image can be reused but configured at run time with different configuration values.
(Changing configuration files requires either different images to be created or using custom volumes which is less ideal in a containerized world).<br>
> So IMHO CDI should provide a simple, natural way to allow environment variables (or system properties) to be easily injected via CDI.<br>
> Delta Spike as a @ConfigProperty annotation which works very nicely<br>
> <a href="http://deltaspike.apache.org/documentation/configuration.html" target="_blank">
http://deltaspike.apache.org/documentation/configuration.html</a><br>
> you can specify a name, default value and use it on an @Inject to provide a value from env vars, system properties or provide a default.<br>
> Given how core and useful this is - it feels like it should be part of the CDI specification; its one simple annotation.<br>
> Currently deltaspike provides a way to configure different sources and whatnot which is cool; I'd be happy if CDI just had a simpler annotation which was only bound to env vars / system properties.<br>
> e.g. @EnvironmentProperty(name = "envvar", deafultValue="cheese")<br>
> There could be debate on whether env vars or system properties should win if the same name is used for both; in a dockerized world I'd prefer env vars to win but folks can always tinker with their run command to make sure they pass in env vars as system properties
to work around this I guess.<br>
<br>
<br>
<br>
--<br>
This message was sent by Atlassian JIRA<br>
(v6.3.11#6341)<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 5 Feb 2015 10:34:49 -0500 (EST)<br>
From: "John Ament (JIRA)" <<a href="mailto:issues@jboss.org" target="_blank">issues@jboss.org</a>><br>
Subject: [cdi-dev] [JBoss JIRA] (CDI-504) have a standard CDI<br>
annotation like @ConfigProperty from deltapsike<br>
To: <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
Message-ID:<br>
<<a href="mailto:JIRA.12562481.1423130482000.45725.1423150489341@Atlassian.JIRA">JIRA.12562481.1423130482000.45725.1423150489341@Atlassian.JIRA</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
<br>
[ <a href="https://issues.jboss.org/browse/CDI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038007#comment-13038007" target="_blank">
https://issues.jboss.org/browse/CDI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038007#comment-13038007</a> ]<br>
<br>
John Ament commented on CDI-504:<br>
--------------------------------<br>
<br>
A separate config JSR has been proposed previously to address this. They want to see more options before trying to standardize it.<br>
<br>
> have a standard CDI annotation like @ConfigProperty from deltapsike<br>
> -------------------------------------------------------------------<br>
><br>
> Key: CDI-504<br>
> URL: <a href="https://issues.jboss.org/browse/CDI-504" target="_blank">
https://issues.jboss.org/browse/CDI-504</a><br>
> Project: CDI Specification Issues<br>
> Issue Type: Feature Request<br>
> Reporter: James Strachan<br>
><br>
> Docker and containerisation is the new hotness; in the docker world images are static and the main way of injecting configuration is via environment variables - so that the same image can be reused but configured at run time with different configuration values.
(Changing configuration files requires either different images to be created or using custom volumes which is less ideal in a containerized world).<br>
> So IMHO CDI should provide a simple, natural way to allow environment variables (or system properties) to be easily injected via CDI.<br>
> Delta Spike as a @ConfigProperty annotation which works very nicely<br>
> <a href="http://deltaspike.apache.org/documentation/configuration.html" target="_blank">
http://deltaspike.apache.org/documentation/configuration.html</a><br>
> you can specify a name, default value and use it on an @Inject to provide a value from env vars, system properties or provide a default.<br>
> Given how core and useful this is - it feels like it should be part of the CDI specification; its one simple annotation.<br>
> Currently deltaspike provides a way to configure different sources and whatnot which is cool; I'd be happy if CDI just had a simpler annotation which was only bound to env vars / system properties.<br>
> e.g. @EnvironmentProperty(name = "envvar", deafultValue="cheese")<br>
> There could be debate on whether env vars or system properties should win if the same name is used for both; in a dockerized world I'd prefer env vars to win but folks can always tinker with their run command to make sure they pass in env vars as system properties
to work around this I guess.<br>
<br>
<br>
<br>
--<br>
This message was sent by Atlassian JIRA<br>
(v6.3.11#6341)<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Thu, 5 Feb 2015 10:39:49 -0500 (EST)<br>
From: "James Strachan (JIRA)" <<a href="mailto:issues@jboss.org" target="_blank">issues@jboss.org</a>><br>
Subject: [cdi-dev] [JBoss JIRA] (CDI-504) have a standard CDI<br>
annotation like @ConfigProperty from deltapsike<br>
To: <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
Message-ID:<br>
<<a href="mailto:JIRA.12562481.1423130482000.45741.1423150789541@Atlassian.JIRA">JIRA.12562481.1423130482000.45741.1423150789541@Atlassian.JIRA</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
<br>
[ <a href="https://issues.jboss.org/browse/CDI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038012#comment-13038012" target="_blank">
https://issues.jboss.org/browse/CDI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038012#comment-13038012</a> ]<br>
<br>
James Strachan commented on CDI-504:<br>
------------------------------------<br>
<br>
@Resource is supported - injecting values from JNDI. I don't see why injecting values (with a default value) from the environment isn't also supported too. There's a Java API for JNDI too so folks could look stuff up in JNDI by hand and do the type conversions
- but we've injection for those values.<br>
<br>
Its also much cleaner code and can easily deal generically with type conversion to long/double/float/date etc.<br>
<br>
Compare:<br>
{code}<br>
@Inject Foo(int bar, ...) {<br>
bar = System.getenv("FOO");<br>
if (bar == null) {<br>
bar = "someDefault";<br>
}<br>
// now convert to a String with error handling....<br>
}<br>
{code}<br>
to just:<br>
{code}<br>
@Inject Foo(@Environment("FOO", "someDefault") int bar, ...) {<br>
}<br>
{code}<br>
<br>
Also by using an annotation it means its very easy to generate documentation and tooling. (e.g. using APT you can know what all the environment variables are used by CDI; either to report on demand or to generate user documentation).<br>
<br>
<br>
<br>
> have a standard CDI annotation like @ConfigProperty from deltapsike<br>
> -------------------------------------------------------------------<br>
><br>
> Key: CDI-504<br>
> URL: <a href="https://issues.jboss.org/browse/CDI-504" target="_blank">
https://issues.jboss.org/browse/CDI-504</a><br>
> Project: CDI Specification Issues<br>
> Issue Type: Feature Request<br>
> Reporter: James Strachan<br>
><br>
> Docker and containerisation is the new hotness; in the docker world images are static and the main way of injecting configuration is via environment variables - so that the same image can be reused but configured at run time with different configuration values.
(Changing configuration files requires either different images to be created or using custom volumes which is less ideal in a containerized world).<br>
> So IMHO CDI should provide a simple, natural way to allow environment variables (or system properties) to be easily injected via CDI.<br>
> Delta Spike as a @ConfigProperty annotation which works very nicely<br>
> <a href="http://deltaspike.apache.org/documentation/configuration.html" target="_blank">
http://deltaspike.apache.org/documentation/configuration.html</a><br>
> you can specify a name, default value and use it on an @Inject to provide a value from env vars, system properties or provide a default.<br>
> Given how core and useful this is - it feels like it should be part of the CDI specification; its one simple annotation.<br>
> Currently deltaspike provides a way to configure different sources and whatnot which is cool; I'd be happy if CDI just had a simpler annotation which was only bound to env vars / system properties.<br>
> e.g. @EnvironmentProperty(name = "envvar", deafultValue="cheese")<br>
> There could be debate on whether env vars or system properties should win if the same name is used for both; in a dockerized world I'd prefer env vars to win but folks can always tinker with their run command to make sure they pass in env vars as system properties
to work around this I guess.<br>
<br>
<br>
<br>
--<br>
This message was sent by Atlassian JIRA<br>
(v6.3.11#6341)<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Thu, 5 Feb 2015 10:49:49 -0500 (EST)<br>
From: "James Strachan (JIRA)" <<a href="mailto:issues@jboss.org" target="_blank">issues@jboss.org</a>><br>
Subject: [cdi-dev] [JBoss JIRA] (CDI-504) have a standard CDI<br>
annotation like @ConfigProperty from deltapsike<br>
To: <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
Message-ID:<br>
<<a href="mailto:JIRA.12562481.1423130482000.45763.1423151389408@Atlassian.JIRA">JIRA.12562481.1423130482000.45763.1423151389408@Atlassian.JIRA</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
<br>
[ <a href="https://issues.jboss.org/browse/CDI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038012#comment-13038012" target="_blank">
https://issues.jboss.org/browse/CDI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038012#comment-13038012</a> ]<br>
<br>
James Strachan edited comment on CDI-504 at 2/5/15 10:49 AM:<br>
-------------------------------------------------------------<br>
<br>
@Resource is supported - injecting values from JNDI. I don't see why injecting values (with a default value) from the environment isn't also supported too. There's a Java API for JNDI too so folks could look stuff up in JNDI by hand and do the type conversions
- but we've injection for those values.<br>
<br>
Its also much cleaner code and can easily deal generically with type conversion to long/double/float/date etc.<br>
<br>
Compare:<br>
{code}<br>
@Inject Foo(int bar, ...) {<br>
bar = System.getenv("FOO");<br>
if (bar == null) {<br>
bar = "someDefault";<br>
}<br>
// now convert the String to an int with nice error handling and reporting....<br>
}<br>
{code}<br>
to just:<br>
{code}<br>
@Inject Foo(@Environment("FOO", "someDefault") int bar, ...) {<br>
}<br>
{code}<br>
<br>
Also by using an annotation it means its very easy to generate documentation and tooling. (e.g. using APT you can know what all the environment variables are used by CDI; either to report on demand or to generate user documentation).<br>
<br>
<br>
<br>
<br>
was (Author: jastrachan):<br>
@Resource is supported - injecting values from JNDI. I don't see why injecting values (with a default value) from the environment isn't also supported too. There's a Java API for JNDI too so folks could look stuff up in JNDI by hand and do the type conversions
- but we've injection for those values.<br>
<br>
Its also much cleaner code and can easily deal generically with type conversion to long/double/float/date etc.<br>
<br>
Compare:<br>
{code}<br>
@Inject Foo(int bar, ...) {<br>
bar = System.getenv("FOO");<br>
if (bar == null) {<br>
bar = "someDefault";<br>
}<br>
// now convert to a String with error handling....<br>
}<br>
{code}<br>
to just:<br>
{code}<br>
@Inject Foo(@Environment("FOO", "someDefault") int bar, ...) {<br>
}<br>
{code}<br>
<br>
Also by using an annotation it means its very easy to generate documentation and tooling. (e.g. using APT you can know what all the environment variables are used by CDI; either to report on demand or to generate user documentation).<br>
<br>
<br>
<br>
> have a standard CDI annotation like @ConfigProperty from deltapsike<br>
> -------------------------------------------------------------------<br>
><br>
> Key: CDI-504<br>
> URL: <a href="https://issues.jboss.org/browse/CDI-504" target="_blank">
https://issues.jboss.org/browse/CDI-504</a><br>
> Project: CDI Specification Issues<br>
> Issue Type: Feature Request<br>
> Reporter: James Strachan<br>
><br>
> Docker and containerisation is the new hotness; in the docker world images are static and the main way of injecting configuration is via environment variables - so that the same image can be reused but configured at run time with different configuration values.
(Changing configuration files requires either different images to be created or using custom volumes which is less ideal in a containerized world).<br>
> So IMHO CDI should provide a simple, natural way to allow environment variables (or system properties) to be easily injected via CDI.<br>
> Delta Spike as a @ConfigProperty annotation which works very nicely<br>
> <a href="http://deltaspike.apache.org/documentation/configuration.html" target="_blank">
http://deltaspike.apache.org/documentation/configuration.html</a><br>
> you can specify a name, default value and use it on an @Inject to provide a value from env vars, system properties or provide a default.<br>
> Given how core and useful this is - it feels like it should be part of the CDI specification; its one simple annotation.<br>
> Currently deltaspike provides a way to configure different sources and whatnot which is cool; I'd be happy if CDI just had a simpler annotation which was only bound to env vars / system properties.<br>
> e.g. @EnvironmentProperty(name = "envvar", deafultValue="cheese")<br>
> There could be debate on whether env vars or system properties should win if the same name is used for both; in a dockerized world I'd prefer env vars to win but folks can always tinker with their run command to make sure they pass in env vars as system properties
to work around this I guess.<br>
<br>
<br>
<br>
--<br>
This message was sent by Atlassian JIRA<br>
(v6.3.11#6341)<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Thu, 5 Feb 2015 10:50:49 -0500 (EST)<br>
From: "James Strachan (JIRA)" <<a href="mailto:issues@jboss.org" target="_blank">issues@jboss.org</a>><br>
Subject: [cdi-dev] [JBoss JIRA] (CDI-504) have a standard CDI<br>
annotation like @ConfigProperty from deltapsike<br>
To: <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
Message-ID:<br>
<<a href="mailto:JIRA.12562481.1423130482000.45773.1423151449139@Atlassian.JIRA">JIRA.12562481.1423130482000.45773.1423151449139@Atlassian.JIRA</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
<br>
[ <a href="https://issues.jboss.org/browse/CDI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038012#comment-13038012" target="_blank">
https://issues.jboss.org/browse/CDI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038012#comment-13038012</a> ]<br>
<br>
James Strachan edited comment on CDI-504 at 2/5/15 10:50 AM:<br>
-------------------------------------------------------------<br>
<br>
@Resource is supported - injecting values from JNDI. I don't see why injecting values (with a default value) from the environment isn't also supported too. There's a Java API for JNDI too so folks could look stuff up in JNDI by hand and do the type conversions
- but we've injection for those values.<br>
<br>
Its also much cleaner code and can easily deal generically with type conversion to long/double/float/date etc.<br>
<br>
Compare:<br>
{code}<br>
int bar;<br>
@Inject Foo() {<br>
barText = System.getenv("FOO");<br>
if (barText == null) {<br>
barText = "someDefault";<br>
}<br>
// now convert the String to an int with nice error handling and reporting....<br>
bar = someConvertCode(barText);<br>
}<br>
{code}<br>
to just:<br>
{code}<br>
@Inject Foo(@Environment("FOO", "someDefault") int bar, ...) {<br>
}<br>
{code}<br>
<br>
Note that in the second case, folks could use the constructor explicitly without being bound to environment variables too; much cleaner, more modular code.<br>
<br>
Also by using an annotation it means its very easy to generate documentation and tooling. (e.g. using APT you can know what all the environment variables are used by CDI; either to report on demand or to generate user documentation).<br>
<br>
<br>
<br>
<br>
was (Author: jastrachan):<br>
@Resource is supported - injecting values from JNDI. I don't see why injecting values (with a default value) from the environment isn't also supported too. There's a Java API for JNDI too so folks could look stuff up in JNDI by hand and do the type conversions
- but we've injection for those values.<br>
<br>
Its also much cleaner code and can easily deal generically with type conversion to long/double/float/date etc.<br>
<br>
Compare:<br>
{code}<br>
@Inject Foo(int bar, ...) {<br>
bar = System.getenv("FOO");<br>
if (bar == null) {<br>
bar = "someDefault";<br>
}<br>
// now convert the String to an int with nice error handling and reporting....<br>
}<br>
{code}<br>
to just:<br>
{code}<br>
@Inject Foo(@Environment("FOO", "someDefault") int bar, ...) {<br>
}<br>
{code}<br>
<br>
Also by using an annotation it means its very easy to generate documentation and tooling. (e.g. using APT you can know what all the environment variables are used by CDI; either to report on demand or to generate user documentation).<br>
<br>
<br>
<br>
> have a standard CDI annotation like @ConfigProperty from deltapsike<br>
> -------------------------------------------------------------------<br>
><br>
> Key: CDI-504<br>
> URL: <a href="https://issues.jboss.org/browse/CDI-504" target="_blank">
https://issues.jboss.org/browse/CDI-504</a><br>
> Project: CDI Specification Issues<br>
> Issue Type: Feature Request<br>
> Reporter: James Strachan<br>
><br>
> Docker and containerisation is the new hotness; in the docker world images are static and the main way of injecting configuration is via environment variables - so that the same image can be reused but configured at run time with different configuration values.
(Changing configuration files requires either different images to be created or using custom volumes which is less ideal in a containerized world).<br>
> So IMHO CDI should provide a simple, natural way to allow environment variables (or system properties) to be easily injected via CDI.<br>
> Delta Spike as a @ConfigProperty annotation which works very nicely<br>
> <a href="http://deltaspike.apache.org/documentation/configuration.html" target="_blank">
http://deltaspike.apache.org/documentation/configuration.html</a><br>
> you can specify a name, default value and use it on an @Inject to provide a value from env vars, system properties or provide a default.<br>
> Given how core and useful this is - it feels like it should be part of the CDI specification; its one simple annotation.<br>
> Currently deltaspike provides a way to configure different sources and whatnot which is cool; I'd be happy if CDI just had a simpler annotation which was only bound to env vars / system properties.<br>
> e.g. @EnvironmentProperty(name = "envvar", deafultValue="cheese")<br>
> There could be debate on whether env vars or system properties should win if the same name is used for both; in a dockerized world I'd prefer env vars to win but folks can always tinker with their run command to make sure they pass in env vars as system properties
to work around this I guess.<br>
<br>
<br>
<br>
--<br>
This message was sent by Atlassian JIRA<br>
(v6.3.11#6341)<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Fri, 6 Feb 2015 05:02:49 -0500 (EST)<br>
From: "Antoine Sabot-Durand (JIRA)" <<a href="mailto:issues@jboss.org" target="_blank">issues@jboss.org</a>><br>
Subject: [cdi-dev] [JBoss JIRA] (CDI-504) have a standard CDI<br>
annotation like @ConfigProperty from deltapsike<br>
To: <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
Message-ID:<br>
<<a href="mailto:JIRA.12562481.1423130482000.47108.1423216969246@Atlassian.JIRA">JIRA.12562481.1423130482000.47108.1423216969246@Atlassian.JIRA</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
<br>
[ <a href="https://issues.jboss.org/browse/CDI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038271#comment-13038271" target="_blank">
https://issues.jboss.org/browse/CDI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038271#comment-13038271</a> ]<br>
<br>
Antoine Sabot-Durand commented on CDI-504:<br>
------------------------------------------<br>
<br>
James, I don't get what's the problem with using DeltaSpike config solution?<br>
<br>
> have a standard CDI annotation like @ConfigProperty from deltapsike<br>
> -------------------------------------------------------------------<br>
><br>
> Key: CDI-504<br>
> URL: <a href="https://issues.jboss.org/browse/CDI-504" target="_blank">
https://issues.jboss.org/browse/CDI-504</a><br>
> Project: CDI Specification Issues<br>
> Issue Type: Feature Request<br>
> Reporter: James Strachan<br>
><br>
> Docker and containerisation is the new hotness; in the docker world images are static and the main way of injecting configuration is via environment variables - so that the same image can be reused but configured at run time with different configuration values.
(Changing configuration files requires either different images to be created or using custom volumes which is less ideal in a containerized world).<br>
> So IMHO CDI should provide a simple, natural way to allow environment variables (or system properties) to be easily injected via CDI.<br>
> Delta Spike as a @ConfigProperty annotation which works very nicely<br>
> <a href="http://deltaspike.apache.org/documentation/configuration.html" target="_blank">
http://deltaspike.apache.org/documentation/configuration.html</a><br>
> you can specify a name, default value and use it on an @Inject to provide a value from env vars, system properties or provide a default.<br>
> Given how core and useful this is - it feels like it should be part of the CDI specification; its one simple annotation.<br>
> Currently deltaspike provides a way to configure different sources and whatnot which is cool; I'd be happy if CDI just had a simpler annotation which was only bound to env vars / system properties.<br>
> e.g. @EnvironmentProperty(name = "envvar", deafultValue="cheese")<br>
> There could be debate on whether env vars or system properties should win if the same name is used for both; in a dockerized world I'd prefer env vars to win but folks can always tinker with their run command to make sure they pass in env vars as system properties
to work around this I guess.<br>
<br>
<br>
<br>
--<br>
This message was sent by Atlassian JIRA<br>
(v6.3.11#6341)<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
<br>
Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other
ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br>
<br>
End of cdi-dev Digest, Vol 51, Issue 9<br>
**************************************<o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
<br>
Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas
provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<o:p></o:p></p>
</div>
</div>
</body>
</html>