Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Sun, 29 May 2016 05:14:12 +0000 (UTC)
From: "Matt Bishop (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <JIRA.12973765.1464498828000.326961.1464498852808@Atlassian.JIRA>
In-Reply-To: <JIRA.12973765.1464498828000@Atlassian.JIRA>
References: <JIRA.12973765.1464498828000@Atlassian.JIRA> <JIRA.12973765.1464498828607@arcas>
Subject: [jira] [Created] (FELIX-5269) ConfigAdmin Web Console plugin does
 not display ConfigurationException messages from DS methods
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 29 May 2016 05:14:14 -0000

Matt Bishop created FELIX-5269:
----------------------------------

             Summary: ConfigAdmin Web Console plugin does not display ConfigurationException messages from DS methods
                 Key: FELIX-5269
                 URL: https://issues.apache.org/jira/browse/FELIX-5269
             Project: Felix
          Issue Type: Bug
          Components: Configuration Admin
    Affects Versions: configadmin-1.8.8
         Environment: Declarative Services with Metatype annotations
            Reporter: Matt Bishop
            Priority: Minor


A bit of setup:

1. A Component has methods annotated with DS @Activate/@Modified and takes an @interface-style configuration object. Looks like this:

{{@Modified public void modified(MyConfig config) throws ConfigurationException {
    if (messedUp(config.thing())) {
        throw new ConfigurationException("thing", "thing is messed up.");
    }
    //carry on with configuration
} }}

2. User opens up Config Admin web console and sees a nice UI to edit 'thing' field for this component. They edit the field in a way that will trigger the ConfigurationException and then 'save' the config.

Expected:
  Web Console UI shows a failure message, and possibly highlights 'thing' to direct attention to the offending field.

Actual:
  Nothing really. Web Console looks like the config is saved.

One note, the exception is logged out. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)