Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Mon, 30 Jul 2012 18:31:35 +0000 (UTC)
From: "Jonathan Anstey (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <2014009343.117200.1343673095267.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1996047156.107466.1343329116224.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (FELIX-3614) In latest webconsole no property
 descriptors are available
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/FELIX-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Anstey updated FELIX-3614:
-----------------------------------

    Attachment: webconsole_metatype_2.patch

Thanks for looking at this Felix. Attaching a patch for suggestion #2. Looks to work similarly to my original patch when I tried this out in Karaf.

Cheers,
Jon
                
> In latest webconsole no property descriptors are available
> ----------------------------------------------------------
>
>                 Key: FELIX-3614
>                 URL: https://issues.apache.org/jira/browse/FELIX-3614
>             Project: Felix
>          Issue Type: Bug
>          Components: Web Console
>    Affects Versions: webconsole-4.0.0
>            Reporter: Jonathan Anstey
>         Attachments: webconsole_metatype.patch, webconsole_metatype_2.patch
>
>
> I noticed that in the latest webconsole (version 4.0.0) all items in the config tab don't have the custom property descriptor shown - just default ones with this message:
> "This form is automatically generated from existing properties because no property descriptors are available for this configuration. This may be cause by the absence of the OSGi Metatype Service or the absence of a MetaType descriptor for this configuration."
> This problem didn't occur in the previous release of 3.1.8.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira