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 441F118C54 for ; Thu, 3 Dec 2015 16:10:57 +0000 (UTC) Received: (qmail 67466 invoked by uid 500); 3 Dec 2015 16:10:56 -0000 Delivered-To: apmail-felix-users-archive@felix.apache.org Received: (qmail 67401 invoked by uid 500); 3 Dec 2015 16:10:56 -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 67388 invoked by uid 99); 3 Dec 2015 16:10:56 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Dec 2015 16:10:56 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 0EBFD1A5C9A for ; Thu, 3 Dec 2015 16:10:56 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3 X-Spam-Level: *** X-Spam-Status: No, score=3 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=liferay-com.20150623.gappssmtp.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id yBUg0RFcuh95 for ; Thu, 3 Dec 2015 16:10:44 +0000 (UTC) Received: from mail-yk0-f172.google.com (mail-yk0-f172.google.com [209.85.160.172]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id CABB520CF5 for ; Thu, 3 Dec 2015 16:10:43 +0000 (UTC) Received: by ykfs79 with SMTP id s79so91678219ykf.1 for ; Thu, 03 Dec 2015 08:10:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=liferay-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=NZpfYHpb0RMgM6YpmNHC2s9RVMfzkXGe2t+lmtbN//0=; b=aTlZCnswssxGrc1LLKuw3wI/Z2KKzw1zgkyaRaYllw3NdZleiglcHC/xuKkWXEt7pk FnZFWQ5VIqRRB8eYbMwbXvqmO9KPsjHXRRtO2cJVjw9k9yCML3j0NM0HHnslzKqel/EZ Q4aQUkA4LyG8G13+z6M4qNsaScy6YY/wcocD/qP8+O9PWgV+AQt80OA/kt4Y55qlQI+6 VEYZ1PJXEHvLBcbYxIzNJW9NTAPqL5tocao4Vz91jvOV1kn6Qw0ITJmbJ2JGZY5RfY+L uLdXEixS7Ozahb5DbJrqEhiaDFszFyGMmO5FR0HtYaxpMduR+VPYeP/CL7UBuQ7CBNcB ahmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=NZpfYHpb0RMgM6YpmNHC2s9RVMfzkXGe2t+lmtbN//0=; b=WjbT8UNi65fG4PCHGQs15bbOlRajSjEhuSfc24Y+fLADYMLGY1RJrpARJMrsfje5Tl yHoN0mggmCGSSPHKIjSujyR4rlpl4FN/oJ4BVUykcLD7KbHBJK5srKK4VOU7mo7esncu aacHc4MBkqItui7BdXfkrar6d9Bzxx8naJvJMcyEFXwFLNG3A5+1Mr9vmshYRSe5HSoU 14AvU5I6BRd5Bl0fq/IgCPxGWdyb9EfQ2+9B6KOBNacKTd0oE262j8GYMRY/9oUgbh/O 6jnG7HNJg81rfWFSv7WSpgVOOMT8VFr/f8JaTzkeoLyDWp67uDCU3PKfa0BE07XjdFaL Swfw== X-Gm-Message-State: ALoCoQlXlqfIQToqqgH4CsJcB8FvJ8Qe9sA15tAdvOlRsgA0f8ekImVwHyK1FvjVvPrY6hjrr0t/ MIME-Version: 1.0 X-Received: by 10.129.101.131 with SMTP id z125mr8128296ywb.184.1449159037033; Thu, 03 Dec 2015 08:10:37 -0800 (PST) Received: by 10.129.98.214 with HTTP; Thu, 3 Dec 2015 08:10:36 -0800 (PST) In-Reply-To: References: Date: Thu, 3 Dec 2015 11:10:36 -0500 Message-ID: Subject: Re: scr:info missing info From: Raymond Auge To: felix users Content-Type: multipart/alternative; boundary=001a114c7958a04bed052600a197 --001a114c7958a04bed052600a197 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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? I would hope to see something like this: -------------------------------- 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: [com.liferay.portal.http.tunnel.configuration.HttpTunnelExtenderConfigurati= on] Services: Service Scope: null Properties: Component Configuration: State: missing g! -------------------------------- make sense now? On Thu, Dec 3, 2015 at 11:03 AM, David Jencks wrote: > 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? > > thanks > david jencks > > > On Dec 3, 2015, at 7:57 AM, Raymond Auge > wrote: > > > > Hey all, > > > > 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: > > > > 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: > > > [com.liferay.portal.http.tunnel.configuration.HttpTunnelExtenderConfigura= tion] > > 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 > > > com.liferay.portal.http.tunnel.configuration.HttpTunnelExtenderConfigurat= ion > > g! > > ---------------------------------- > > > > And here is the report when NO required configuration is available: > > > > ---------------------------------- > > 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: > > > [com.liferay.portal.http.tunnel.configuration.HttpTunnelExtenderConfigura= tion] > > Services: Service Scope: null > > Properties: > > g! > > ---------------------------------- > > > > As you can see it's not clear at all that the component is missing the > > configuration it requires. > > > > Can we fix this? > > > > -- > > *Raymond Aug=C3=A9* > > (@rotty3000) > > Senior Software Architect *Liferay, Inc.* > > (@Liferay) > > Board Member & EEG Co-Chair, OSGi Alliance > (@OSGiAlliance) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org > For additional commands, e-mail: users-help@felix.apache.org > > --=20 *Raymond Aug=C3=A9* (@rotty3000) Senior Software Architect *Liferay, Inc.* (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance (@OSGiAlliance= ) --001a114c7958a04bed052600a197--