Return-Path: X-Original-To: apmail-felix-dev-archive@www.apache.org Delivered-To: apmail-felix-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E509618974 for ; Wed, 18 Nov 2015 19:59:13 +0000 (UTC) Received: (qmail 54202 invoked by uid 500); 18 Nov 2015 19:59:12 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 53947 invoked by uid 500); 18 Nov 2015 19:59:12 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 53520 invoked by uid 99); 18 Nov 2015 19:59:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Nov 2015 19:59:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 48EF02C1F73 for ; Wed, 18 Nov 2015 19:59:11 +0000 (UTC) Date: Wed, 18 Nov 2015 19:59:11 +0000 (UTC) From: "Carsten Ziegeler (JIRA)" To: dev@felix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FELIX-5105) Web Console configuration does not appear in configurations MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FELIX-5105?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1501= 1849#comment-15011849 ]=20 Carsten Ziegeler commented on FELIX-5105: ----------------------------------------- The strange thing is, even these scenarios work for me. The webconsole is registering a service factory and the framework does all = the magic to instantiate the provider service dynamically. Right now I can'= t see a difference in our setup > Web Console configuration does not appear in configurations > ----------------------------------------------------------- > > Key: FELIX-5105 > URL: https://issues.apache.org/jira/browse/FELIX-5105 > Project: Felix > Issue Type: Bug > Components: Web Console > Affects Versions: webconsole-4.2.14 > Reporter: Miroslav =C5=A0ulc > Labels: patch > Attachments: metatype.xml.patch > > > since some time web console configuration is more and more broken it seem= s. there is for example bug related to lost localization of the configurati= on which i encountered on my installations too. in some cases it also happe= ns that the web console configuration is not displayed at all. in fact i wa= s not able to display it (and so edit it) at all. i tried to debug the issu= e but the only thing i found is that for some (to me) unknown reason the co= nfiguration from java class is not picked up. > in version 4.2.15-SNAPSHOT and older versions the metatype provider is im= plemented as java class org.apache.felix.webconsole.internal.servlet.Config= urationMetatypeSupport. that is probably the cause of the problem that the = configuration usually does not load, maybe because of some synchronization = issue. i noticed some information about attempts to fix it in previous vers= ions of web console but these were just attempts as the issue persists. > i have no idea why the metatype provider is implemented using Configurati= onMetatypeSupport class instead of using metatype.xml file which would be m= ore transparent and easier to manage, maybe it's for historical reason when= metatype implementation was not that capable as it is now. > so i created metatype.xml file that defines the same configuration as is = done using ConfigurationMetatypeSupport and it seems to work fine. i did no= t remove the ConfigurationMetatypeSupport and related code though as i gues= s it would be better done by someone who better understands the code. > i will try to attach the patch i have if i find out how. -- This message was sent by Atlassian JIRA (v6.3.4#6332)