Return-Path: X-Original-To: apmail-felix-users-archive@minotaur.apache.org Delivered-To: apmail-felix-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B7B5518398 for ; Thu, 3 Dec 2015 18:00:30 +0000 (UTC) Received: (qmail 5800 invoked by uid 500); 3 Dec 2015 18:00:30 -0000 Delivered-To: apmail-felix-users-archive@felix.apache.org Received: (qmail 5746 invoked by uid 500); 3 Dec 2015 18:00:30 -0000 Mailing-List: contact users-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@felix.apache.org Delivered-To: mailing list users@felix.apache.org Received: (qmail 5734 invoked by uid 99); 3 Dec 2015 18:00:29 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Dec 2015 18:00:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 713F0C0BE2 for ; Thu, 3 Dec 2015 18:00:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 5.144 X-Spam-Level: ***** X-Spam-Status: No, score=5.144 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_MSGID_YAHOO=2.244, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Q-D_pL6H6rsZ for ; Thu, 3 Dec 2015 18:00:15 +0000 (UTC) Received: from mail-pf0-f176.google.com (mail-pf0-f176.google.com [209.85.192.176]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 696D624E19 for ; Thu, 3 Dec 2015 18:00:14 +0000 (UTC) Received: by pfnn128 with SMTP id n128so11931651pfn.0 for ; Thu, 03 Dec 2015 10:00:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to; bh=lYvQWBgf+82q9JG7BHWr/NfZ0h/XWt9opCUOwHyrUyk=; b=s4meEmniqtrbn+pobmw9w7MPy79g3Ge5tDRZeHbzwsWjCZr0vlPjZiXjdRCiEqnLLY pl61r3kvfd3BjfJWDXCqBlY/s0gP0DuXeWztkpGSy9n9dn6n+K8kWAweefGqDizs2EVu 73ha4fsceVC1ftQ3qQAnqARlGQCch3wdhXgVP90X4bTmeDdiW1IrQ6TluIvaflkjc05Z bQDUZ9xH9iFCCekhLKD1YkXOQnLEN/DFxhoRdYaQBEQhuPKRJxTT+EMXp2TgLQsLQgr/ xRQ6mKgxxlXTyVidKrRUDX9ixcELkKbjhphSP7KA0FxEDTiv8k2ya6mTSnP42DlcHprp M6QQ== X-Received: by 10.98.67.201 with SMTP id l70mr14912911pfi.29.1449165606470; Thu, 03 Dec 2015 10:00:06 -0800 (PST) Received: from [10.0.1.6] (c-98-246-196-64.hsd1.or.comcast.net. [98.246.196.64]) by smtp.gmail.com with ESMTPSA id qy7sm12057101pab.37.2015.12.03.10.00.05 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 03 Dec 2015 10:00:05 -0800 (PST) From: David Jencks X-Google-Original-From: David Jencks Content-Type: multipart/alternative; boundary="Apple-Mail=_EE1A17D0-1E94-40E9-BAD8-F9B5FF335603" Message-Id: <3CEB8963-E4DD-45F5-8E4F-8F87E05273D7@yahoo.com> Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: scr:info missing info Date: Thu, 3 Dec 2015 09:59:57 -0800 References: <870CF870-6CF3-42E0-8606-65E32FCF3FA9@yahoo.com> To: users@felix.apache.org In-Reply-To: X-Mailer: Apple Mail (2.2104) --Apple-Mail=_EE1A17D0-1E94-40E9-BAD8-F9B5FF335603 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Since the Component Configuration: header appears for each component = configuration, I might prefer =E2=80=A6 (No Component Configuration) I think I=E2=80=99d leave this out when the component is disabled as an = additional clue about the state. WDYT? thanks david jencks > On Dec 3, 2015, at 9:50 AM, Raymond Auge = wrote: >=20 > On Thu, Dec 3, 2015 at 12:31 PM, David Jencks = > > wrote: >=20 >> well, to me it did state that quite plainly: >>=20 >>>>>> Configuration Policy: require >>=20 >=20 >=20 > but that's not showing that it's "waiting" for something... only that = one > is required... Does it have any right now? >=20 > In your configuration list maybe all you need is: >=20 > ----------------- > ... > Configuration Policy: require > ... > Component Configuration: none > ----------------- >=20 > That's not redundant. >=20 > It's a) indicating that it does indeed need something before it does > anything b) it doesn't have anything right now. >=20 > I'd be totally satisfied with that. At least it would allow for a = quick > scan of the output to observe that it's just not configured!! >=20 >=20 >=20 >> I look forward to your suggestions. >>=20 >> thanks >> david jencks >>=20 >>> On Dec 3, 2015, at 9:12 AM, Raymond Auge >> wrote: >>>=20 >>> The point is that it took me and a technical support person about 15 >>> minutes to figure out (this is not a module I wrote) why the = component >>> wasn't "activating". >>>=20 >>> If scr:info had inferred that "hey, this thing won't do anything = until it >>> receives at least ONE configuration" it would have really helped us, = and >> I >>> would have had more encouraging response than ... I guess you need = to >> infer >>> from the obscure messaging that it's in a "waiting" state. >>>=20 >>> I'll see what I can come up with. >>>=20 >>> - Ray >>>=20 >>> On Thu, Dec 3, 2015 at 11:56 AM, David Jencks = >>> wrote: >>>=20 >>>> Hi Ray, >>>>=20 >>>> You are confusing a lot of terms :-) >>>>=20 >>>> =E2=80=9Cenabled=E2=80=9D is a component description state. If the = component is >> disabled, >>>> whether there are CA configurations for it and required = dependencies >>>> present or missing is completely irrelevant because DS isn=E2=80=99t = even >> looking >>>> at that yet. >>>>=20 >>>> Once the component is enabled, then there=E2=80=99s a chance that = you might bet >>>> one or more instances of the component=E2=80=A6.. component = configurations, not >> to >>>> be confused with CA configurations. >>>>=20 >>>> Depending on the configuration policy=E2=80=A6. >>>> ignored >> one component configuration. This will be satisfied if = all >> the >>>> required references are satisfied and result in (one or more) = instances >>>> depending on the scope, immediate setting, and whether there are = any >> users >>>> of the exposed service (if any) >>>>=20 >>>> optionsl >> one or more component configurations depending on CA >>>> configurations. Each one will be satisfied or not depending on = it=E2=80=99s >>>> references, and again instances depend on scope, etc etc. You can = see >>>> whether the one configuration is configured from CA by looking at = the >>>> properties for a pid/factory pid. >>>>=20 >>>> required >> 0 or more component configurations, one per CA >> configuration. >>>> Each one will be satisfied or not depending on its references etc = etc. >>>>=20 >>>> So, there are a lot of moving parts here. I=E2=80=99m not sure = it=E2=80=99s practical >> to >>>> explain the entire DS model in the output of scr:info, which I = think is >>>> what you=E2=80=99re aiming for. However I=E2=80=99m happy to = consider suggestions that >> are >>>> actually in line with the model. I haven=E2=80=99t been able to = figure out >>>> improvements to what is there that actually seem to me to provide = more >>>> information without being very redundant and more confusing. Maybe = you >>>> will have better luck. >>>>=20 >>>> thanks >>>> david jencks >>>>=20 >>>>> On Dec 3, 2015, at 8:19 AM, Raymond Auge = >>>> wrote: >>>>>=20 >>>>> Furthermore in looking at the >>>>>=20 >>>>> scr:list | grep >>>>>=20 >>>>> it produces >>>>>=20 >>>>> [com.liferay.portal.http.tunnel.extender.HttpTunnelExtender] [ = 60] >>>> [true] >>>>>=20 >>>>> which seems to indicate that it's enabled... which it's not = really. >>>>>=20 >>>>> - Ray >>>>>=20 >>>>> On Thu, Dec 3, 2015 at 11:10 AM, Raymond Auge < >> raymond.auge@liferay.com> >>>>> wrote: >>>>>=20 >>>>>> The point is that if you start with no configuration, and you = view the >>>>>> component scr:info it's hard for a less knowledgeable person to >>>> recognize >>>>>> that it's missing a configuration? >>>>>>=20 >>>>>> I would hope to see something like this: >>>>>>=20 >>>>>> -------------------------------- >>>>>> g! scr:info = com.liferay.portal.http.tunnel.extender.HttpTunnelExtender >>>>>> *** Bundle: com.liferay.portal.http.tunnel.extender (60) >>>>>> Component Description: >>>>>> Name: com.liferay.portal.http.tunnel.extender.HttpTunnelExtender >>>>>> Default State: enabled >>>>>> Activation: immediate >>>>>> Configuration Policy: require >>>>>> Activate Method: activate >>>>>> Deactivate Method: deactivate >>>>>> Modified Method: modified >>>>>> Configuration Pid: >>>>>>=20 >>>>=20 >> = [com.liferay.portal.http.tunnel.configuration.HttpTunnelExtenderConfigurat= ion] >>>>>> Services: Service Scope: null >>>>>> Properties: >>>>>> Component Configuration: >>>>>> State: missing >>>>>> g! >>>>>> -------------------------------- >>>>>>=20 >>>>>> make sense now? >>>>>>=20 >>>>>>=20 >>>>>> On Thu, Dec 3, 2015 at 11:03 AM, David Jencks < >> david.a.jencks@gmail.com >>>>>=20 >>>>>> wrote: >>>>>>=20 >>>>>>> It looks pretty blatant to me that the reason there are no = component >>>>>>> configurations is that there is no CA configuration. What kind = of >>>>>>> notification do you want? >>>>>>>=20 >>>>>>> thanks >>>>>>> david jencks >>>>>>>=20 >>>>>>>> On Dec 3, 2015, at 7:57 AM, Raymond Auge = >>>>>>> wrote: >>>>>>>>=20 >>>>>>>> Hey all, >>>>>>>>=20 >>>>>>>> It seems that scr:info report is not clearly indicating when a >>>> required >>>>>>>> configuration is not available. It is showing good info when = the >>>>>>> component >>>>>>>> has a configuration: >>>>>>>>=20 >>>>>>>> Here is the report WITH required configuration: >>>>>>>> ---------------------------------- >>>>>>>> g! scr:info >> com.liferay.portal.http.tunnel.extender.HttpTunnelExtender >>>>>>>> *** Bundle: com.liferay.portal.http.tunnel.extender (60) >>>>>>>> Component Description: >>>>>>>> Name: = com.liferay.portal.http.tunnel.extender.HttpTunnelExtender >>>>>>>> Default State: enabled >>>>>>>> Activation: immediate >>>>>>>> Configuration Policy: require >>>>>>>> Activate Method: activate >>>>>>>> Deactivate Method: deactivate >>>>>>>> Modified Method: modified >>>>>>>> Configuration Pid: >>>>>>>>=20 >>>>>>>=20 >>>>=20 >> = [com.liferay.portal.http.tunnel.configuration.HttpTunnelExtenderConfigurat= ion] >>>>>>>> Services: Service Scope: null >>>>>>>> Properties: >>>>>>>> Component Configuration: >>>>>>>> ComponentId: 1936 >>>>>>>> State: active >>>>>>>> Properties: >>>>>>>> component.id =3D 1936 >>>>>>>> component.name =3D >>>>>>>> com.liferay.portal.http.tunnel.extender.HttpTunnelExtender >>>>>>>> hostsAllowed =3D [127.0.0.1] >>>>>>>> service.pid =3D >>>>>>>>=20 >>>>>>>=20 >>>>=20 >> = com.liferay.portal.http.tunnel.configuration.HttpTunnelExtenderConfigurati= on >>>>>>>> g! >>>>>>>> ---------------------------------- >>>>>>>>=20 >>>>>>>> And here is the report when NO required configuration is = available: >>>>>>>>=20 >>>>>>>> ---------------------------------- >>>>>>>> g! scr:info >> com.liferay.portal.http.tunnel.extender.HttpTunnelExtender >>>>>>>> *** Bundle: com.liferay.portal.http.tunnel.extender (60) >>>>>>>> Component Description: >>>>>>>> Name: = com.liferay.portal.http.tunnel.extender.HttpTunnelExtender >>>>>>>> Default State: enabled >>>>>>>> Activation: immediate >>>>>>>> Configuration Policy: require >>>>>>>> Activate Method: activate >>>>>>>> Deactivate Method: deactivate >>>>>>>> Modified Method: modified >>>>>>>> Configuration Pid: >>>>>>>>=20 >>>>>>>=20 >>>>=20 >> = [com.liferay.portal.http.tunnel.configuration.HttpTunnelExtenderConfigurat= ion] >>>>>>>> Services: Service Scope: null >>>>>>>> Properties: >>>>>>>> g! >>>>>>>> ---------------------------------- >>>>>>>>=20 >>>>>>>> As you can see it's not clear at all that the component is = missing >> the >>>>>>>> configuration it requires. >>>>>>>>=20 >>>>>>>> Can we fix this? >>>>>>>>=20 >>>>>>>> -- >>>>>>>> *Raymond Aug=C3=A9* = >>>>>>>> (@rotty3000) >>>>>>>> Senior Software Architect *Liferay, Inc.* = >>>>>>>> (@Liferay) >>>>>>>> Board Member & EEG Co-Chair, OSGi Alliance >>>>>>> (@OSGiAlliance) >>>>>>>=20 >>>>>>>=20 >>>>>>> = --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org >>>>>>> For additional commands, e-mail: users-help@felix.apache.org >>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> -- >>>>>> *Raymond Aug=C3=A9* = >>>>>> (@rotty3000) >>>>>> Senior Software Architect *Liferay, Inc.* = >>>>>> (@Liferay) >>>>>> Board Member & EEG Co-Chair, OSGi Alliance >>>>>> (@OSGiAlliance) >>>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> -- >>>>> *Raymond Aug=C3=A9* = >>>>> (@rotty3000) >>>>> Senior Software Architect *Liferay, Inc.* >>>>> (@Liferay) >>>>> Board Member & EEG Co-Chair, OSGi Alliance >>>> (@OSGiAlliance) >>>>=20 >>>>=20 >>>> = --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org >>>> For additional commands, e-mail: users-help@felix.apache.org >>>>=20 >>>>=20 >>>=20 >>>=20 >>> -- >>> *Raymond Aug=C3=A9* = >>> (@rotty3000) >>> Senior Software Architect *Liferay, Inc.* >>> (@Liferay) >>> Board Member & EEG Co-Chair, OSGi Alliance >> (@OSGiAlliance) >>=20 >>=20 >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org = >> For additional commands, e-mail: users-help@felix.apache.org = >>=20 >>=20 >=20 >=20 > --=20 > *Raymond Aug=C3=A9* > > (@rotty3000) > Senior Software Architect *Liferay, Inc.* > > (@Liferay) > Board Member & EEG Co-Chair, OSGi Alliance > (@OSGiAlliance) --Apple-Mail=_EE1A17D0-1E94-40E9-BAD8-F9B5FF335603--