Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id F1A6A200C51 for ; Sat, 25 Mar 2017 15:37:09 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id F05A1160B7B; Sat, 25 Mar 2017 14:37:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 47750160B88 for ; Sat, 25 Mar 2017 15:37:09 +0100 (CET) Received: (qmail 96131 invoked by uid 500); 25 Mar 2017 14:37:03 -0000 Mailing-List: contact users-help@deltaspike.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@deltaspike.apache.org Delivered-To: mailing list users@deltaspike.apache.org Received: (qmail 95509 invoked by uid 99); 25 Mar 2017 14:37:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Mar 2017 14:37:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 95E8C181069 for ; Sat, 25 Mar 2017 14:37:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.679 X-Spam-Level: X-Spam-Status: No, score=0.679 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.de Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id vqU0yT6TFpeR for ; Sat, 25 Mar 2017 14:36:59 +0000 (UTC) Received: from nm29-vm3.bullet.mail.ne1.yahoo.com (nm29-vm3.bullet.mail.ne1.yahoo.com [98.138.91.159]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 6B0B55FAC6 for ; Sat, 25 Mar 2017 14:36:58 +0000 (UTC) Received: from [98.138.100.117] by nm29.bullet.mail.ne1.yahoo.com with NNFMP; 25 Mar 2017 14:36:48 -0000 Received: from [98.138.226.130] by tm108.bullet.mail.ne1.yahoo.com with NNFMP; 25 Mar 2017 14:36:48 -0000 Received: from [127.0.0.1] by smtp217.mail.ne1.yahoo.com with NNFMP; 25 Mar 2017 14:36:48 -0000 X-Yahoo-Newman-Id: 131693.57257.bm@smtp217.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: PZHJ.S8VM1mzX7Ig1ky1fc9fkqWfYB9a_ayyv4NkZ28InjN 4lsdBufmHbA5P80s0.IKiuPGAlFwQQ_eLv5JIf_DKOIPp5aHuXxGb5pnRE4_ pqXQf2D5cHlslBoZmXmKabOoEJ2Uewvs.vikJmC0U55r.0tqji_U2FID5E1_ u9VPy3a9fxik3t6NFRBu4VlzX4_8nhmG.Rvp429hm5pz8LCITjekonZzWmey PU0JJLWz01R9aw9lIqlqphXVMx4HMvU958TuMSznxADdnu_wVRC61zfr1UvR 0e.ZcFpacCihzu05v5FZynaTiy6i41mtoPlwCr5oq7D29CgmabbUgX4bdQKL l0SgdrJo5DLHQES2rYiX9W7Qmsq7YkCx2CG.aVs86umoYybLhMx29Xvvp9fq 2Ad3Que5PTSjgZKrWyDOXGLCPClDCZ38vK.mO6DTSenTPfx8p6HGmAAkMcEf sY2bAoJ_xjZSfJyOC6pgnOe9x81p0qoR5tGA1lGdIrhdSrJm0znNPIHRwmY3 NGVWpx4p9.xPoOcHS0srD.M3Gpacz1S8eXrHVEWM- X-Yahoo-SMTP: 81dhI.iswBBq7boyzRoOX6xuRIe8 From: Mark Struberg Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Howto use DeltaSpike Configuration Module for userprofiles Date: Sat, 25 Mar 2017 15:36:48 +0100 References: <62FA03FC-3530-4CA8-9147-07A1C9DE5C16@yahoo.de> To: users@deltaspike.apache.org In-Reply-To: Message-Id: <609CE16D-64DC-44DB-BB24-A9A76C6D259C@yahoo.de> X-Mailer: Apple Mail (2.3259) archived-at: Sat, 25 Mar 2017 14:37:10 -0000 I did reread the original post again and I think I had a different = picture in mind. In my reply, I was thinking about the following use case: mycomp.somebatch.error.emails=3Da@mycomp,b@mycomp,c@mycomp List emails =3D = ConfigResolver.resolve("mycomp.somebatch.error.emails).getListValue(); or=20 mycomp.someprocess.retry.times=3D30, 60,180,600 List retryTimes =3D = ConfirResolver.resolve("mycomp.someprocess.retry.times").as(Integer.class)= .getListValue(); But those 'lists' are something different than Thomas Lustig meant I = think (after reading again). This is close to what I had as 'lookupChain' in my Config JSR proposal. It is basically the same like ProjectStageAware and PropertyAware, but = abstracted out to be attribute independent. Something like String val =3D ConfigProvider.resolve("some.key). withLookupChain("${deltaspike.ProjectStage}", "${profile_key}, = "postgres") .getValue(); This will kind of go through the matrix in a bitwise fashion and check = for existing post-fixes like described in [1]. Just fully dynamic. If the value contains a ${} then it is a variable which will get = evaluated first. Without it's just a hardcoded postfix. makes sense? LieGrue, strub [1] = https://deltaspike.apache.org/javadoc/1.7.1/org/apache/deltaspike/core/api= /config/ConfigResolver.html#getPropertyAwarePropertyValue-java.lang.String= -java.lang.String- > Am 25.03.2017 um 05:15 schrieb John D. Ament : >=20 > Hi, >=20 > I'm not sure that config is necessarily the same as a preferences API. > Specifically, you want to store use specific attribute values, if I'm > understanding you right, correct? >=20 > John >=20 > On Fri, Mar 24, 2017 at 2:02 PM Mark Struberg = > wrote: >=20 >> Hi folks! >>=20 >> I've implemented a comma separated List handling already, just didn't >> commit it yet. >> Will try to push it over the weekend and put it up for review. >>=20 >> LieGrue, >> strub >>=20 >>=20 >>> Am 23.03.2017 um 09:04 schrieb Pawel.Maczka@b-m.pl: >>>=20 >>> This could be a great feature. After a small research there are only >>> native Java Preferences ( hate that ) or self made. But it is very = common >>> and fits in DS suite in my opinion. >>>=20 >>> Pawe=C5=82 >>>=20 >>>=20 >>>=20 >>>=20 >>> Od: Thomas Lustig >>> Do: users@deltaspike.apache.org >>> Data: 2017-03-19 10:14 >>> Temat: Howto use DeltaSpike Configuration Module for userprofiles >>>=20 >>>=20 >>>=20 >>> Dear Community, >>>=20 >>> I am really fond of using Deltaspike configuration module to = configure my >>> JEE application. >>> I would like to store also data that is specific to application = users in >> a >>> kind of profile. >>>=20 >>> config_key profile_key = config_value >>>=20 >> = --------------------------------------------------------------------------= ---------------------------- >>> john favorite_menues my_books,my_posts >>> eliza favorite_menues my_posts,my_music >>>=20 >>>=20 >>> Are there some best practises how to implement such an additional >>> dimension >>> (profile_key) using deltaspike? >>>=20 >>> Thanking you very much in advance for helping me >>>=20 >>> kind regards >>>=20 >>> Tom >>>=20 >>=20 >>=20