[jira] [Updated] (FELIX-5269) ConfigAdmin Web Console plugin does not display ConfigurationException messages from DS methods
[
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)
[jira] [Created] (FELIX-5269) ConfigAdmin Web Console plugin does not display ConfigurationException messages from DS methods
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)
[RESULT] [VOTE] SCR Tooling Bnd Plugin 1.5.0
Hi, The vote has passed with the following result : +1 (binding): Carsten Ziegeler, Clement Escoffier, Pierre De Rop +1 (non binding): I will copy this release to the Felix dist directory and promote the artifacts to the central Maven repository. Thanks for your votes. cheers; /Pierre
Re: [VOTE] SCR Tooling Bnd Plugin 1.5.0
+1 /Pierre On Mon, May 23, 2016 at 8:15 AM, Clement Escoffier < clement.escoff...@gmail.com> wrote: > +1, > > Regards, > > Clement > > > On 23 mai 2016, at 07:19, Carsten Ziegeler wrote: > > > > +1 > > > > Thanks > > Carsten > > -- > > Carsten Ziegeler > > Adobe Research Switzerland > > cziege...@apache.org > >
[jira] [Resolved] (FELIX-5268) Service not unregistered while bundle is starting
[ https://issues.apache.org/jira/browse/FELIX-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop resolved FELIX-5268. -- Resolution: Fixed Issue fixed in revision 1745605 > Service not unregistered while bundle is starting > - > > Key: FELIX-5268 > URL: https://issues.apache.org/jira/browse/FELIX-5268 > Project: Felix > Issue Type: Bug > Components: Dependency Manager >Affects Versions: org.apache.felix.dependencymanager-r1 >Reporter: Pierre De Rop >Assignee: Pierre De Rop > Fix For: org.apache.felix.dependencymanager-r9 > > > This bug has been reported by Bram from the felix users mailing list: > http://www.mail-archive.com/users%40felix.apache.org/msg17269.html > -> When a bundle is starting, and if a service providing component is added > from the Activator, then if the component is losing a required service > dependency or if the component is intentionally removed from the activator, > then the DM component is stopped, but any services provided by the component > are not unregistered from the service registry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-5268) Service not unregistered while bundle is starting
[ https://issues.apache.org/jira/browse/FELIX-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305606#comment-15305606 ] Pierre De Rop commented on FELIX-5268: -- Added test case in revision 1745936: Adding src/org/apache/felix/dm/itest/api/FELIX5268_AddRemoveServiceTest.java Adding src/org/apache/felix/dm/itest/bundle2 Adding src/org/apache/felix/dm/itest/bundle2/Activator.java Adding src/org/apache/felix/dm/itest/bundle2/AddRemoveService.java Adding src/org/apache/felix/dm/itest/bundle2/packageinfo > Service not unregistered while bundle is starting > - > > Key: FELIX-5268 > URL: https://issues.apache.org/jira/browse/FELIX-5268 > Project: Felix > Issue Type: Bug > Components: Dependency Manager >Affects Versions: org.apache.felix.dependencymanager-r1 >Reporter: Pierre De Rop >Assignee: Pierre De Rop > Fix For: org.apache.felix.dependencymanager-r9 > > > This bug has been reported by Bram from the felix users mailing list: > http://www.mail-archive.com/users%40felix.apache.org/msg17269.html > -> When a bundle is starting, and if a service providing component is added > from the Activator, then if the component is losing a required service > dependency or if the component is intentionally removed from the activator, > then the DM component is stopped, but any services provided by the component > are not unregistered from the service registry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-5268) Service not unregistered while bundle is starting
Pierre De Rop created FELIX-5268: Summary: Service not unregistered while bundle is starting Key: FELIX-5268 URL: https://issues.apache.org/jira/browse/FELIX-5268 Project: Felix Issue Type: Bug Components: Dependency Manager Affects Versions: org.apache.felix.dependencymanager-r1 Reporter: Pierre De Rop Assignee: Pierre De Rop Fix For: org.apache.felix.dependencymanager-r9 This bug has been reported by Bram from the felix users mailing list: http://www.mail-archive.com/users%40felix.apache.org/msg17269.html -> When a bundle is starting, and if a service providing component is added from the Activator, then if the component is losing a required service dependency or if the component is intentionally removed from the activator, then the DM component is stopped, but any services provided by the component are not unregistered from the service registry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
