[
https://issues.apache.org/jira/browse/FELIX-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Bishop updated FELIX-5269:
-------------------------------
Description:
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.
was:
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.
> 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)
