[jira] [Updated] (FELIX-3910) Race conditions in DependencyManager

[Pierre De Rop (JIRA)]

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

Pierre De Rop updated FELIX-3910:
-

Attachment: FELIX-3910.patch.3

Attached an third version of the patch (FELIX-3910.patch.3), which has been 
aligned with recent commit made by Xander, in revision r1488970.

> Race conditions in DependencyManager
> 
>
> Key: FELIX-3910
> URL: https://issues.apache.org/jira/browse/FELIX-3910
> Project: Felix
>  Issue Type: Bug
>  Components: Dependency Manager
>Affects Versions: dependencymanager-3.0.0
> Environment: jdk1.6, jdk1.7, linux fc16
>Reporter: Pierre De Rop
> Attachments: FELIX-3910-patch, FELIX-3910.patch.2, FELIX-3910.patch.3
>
>
> In a multi threaded context, where dependencies are injected concurrently 
> from different threads, we  came across some exceptions which seem to take 
> place from dependencymanager.
> I have tried to reproduce the problems using a paxexam test which I will 
> commit.
> Not all exceptions are reproduced by the test case, but I think that the 
> testcase really reproduces a problem. 
> I also have a candidate patch, which I will submit to this jira issue.
> Here are the exceptions we have seen:
> first stacktrace seen:
> ===
> ERROR: Bundle test.dm [21] EventDispatcher: Error during dispatch. 
> (java.lang.NullPointerException)
> java.lang.NullPointerException
> at 
> org.apache.felix.dm.impl.dependencies.ServiceDependencyImpl.addedService(ServiceDependencyImpl.java:481)
> at 
> org.apache.felix.dm.tracker.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1325)
> at 
> org.apache.felix.dm.tracker.AbstractTracked.trackAdding(AbstractTracked.java:290)
> at 
> org.apache.felix.dm.tracker.AbstractTracked.track(AbstractTracked.java:236)
> at 
> org.apache.felix.dm.tracker.ServiceTracker$Tracked.serviceChangedHideAspects(ServiceTracker.java:1206)
> at 
> org.apache.felix.dm.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1101)
> at 
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)
> at 
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)
> at 
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4260)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3275)
> at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)
> at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:320)
> at test.dm.race.RaceTest$RegistrationHelper$1.run(RaceTest.java:104)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> second exceptions:
> ==
> ERROR: EventDispatcher: Error during dispatch. 
> (java.lang.NullPointerException)
> java.lang.NullPointerException
> at 
> org.apache.felix.dm.impl.ComponentImpl.invokeCallbackMethod(ComponentImpl.java:686)
> at 
> org.apache.felix.dm.impl.dependencies.ServiceDependencyImpl.invoke(ServiceDependencyImpl.java:704)
> at 
> org.apache.felix.dm.impl.dependencies.ServiceDependencyImpl.invokeRemoved(ServiceDependencyImpl.java:666)
> at 
> org.apache.felix.dm.impl.dependencies.ServiceDependencyImpl.removedService(ServiceDependencyImpl.java:520)
> at 
> org.apache.felix.dm.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:1351)
> at 
> org.apache.felix.dm.tracker.AbstractTracked.untrack(AbstractTracked.java:359)
> at 
> org.apache.felix.dm.tracker.ServiceTracker$Tracked.serviceChangedHideAspects(ServiceTracker.java:1285)
> at 
> org.apache.felix.dm.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1101)
> at 
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:878)
> at 
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:732)
> at 
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3587)
> at org.apache.felix.framework.Felix.access$000(Felix.java:40)
> at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:625)
> at 
> org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:117)
> at 
> org.a

Re: DP WebConsole suggestion (Was: Re: [VOTE] Release DeploymentAdmin 0.9.4 and AutoConf Processor 0.1.4)

[Pierre De Rop]

Ok, I reopened the
FELIX-3861issue.

regards;
/Pierre

On Mon, Jun 3, 2013 at 12:37 PM, Marcel Offermans <
marcel.offerm...@luminis.nl> wrote:

> On Jun 3, 2013, at 12:32 PM, Pierre De Rop  wrote:
>
> > A minor remark regarding the DP webconsole plugin (not concerned by this
> > candidate release), I see that DP is located in the "Main" tab instead of
> > the "OSGi" tab.
> > May be I should open a jira issue for moving DP in the "OSGi" webconsole
> > tab section ?
>
> That makes sense, Pierre, please do open an issue for that!
>
> Greetings, Marcel
>
>

[jira] [Reopened] (FELIX-3861) Set felix.webconsole.category on Web Console plugins

[Pierre De Rop (JIRA)]

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

Pierre De Rop reopened FELIX-3861:
--


I reopen this issue because it seems that some "OSGi" plugins are not yet fully 
updated in order to use the correct "OSGi" category.

For example, the "deppack" plugin is still registered in the default "Main" 
category, and should override the "getCatory" method in order to use the "OSGi" 
category.

> Set felix.webconsole.category on Web Console plugins
> 
>
> Key: FELIX-3861
> URL: https://issues.apache.org/jira/browse/FELIX-3861
> Project: Felix
>  Issue Type: Improvement
>  Components: Web Console
>Affects Versions: webconsole-ds-plugin-1.0.0, webconsole-4.0.0
>Reporter: Felix Meschberger
>Assignee: Felix Meschberger
> Fix For: webconsole-gogo-plugin-1.0.0, 
> webconsole-ds-plugin-1.0.2, webconsole-4.2.0
>
>
> The Web Console supports categories and our plugins in the webconsole-plugins 
> folder should use them.
> The SimpleWebConsolePlugin should also use the getter methods to get the 
> title, label, and optional category for registration.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [VOTE] Apache Felix Web Console 4.2.0 and Inventory Printer 1.0.0

[Pierre De Rop]

Hi Felix,

Regarding this FELIX-3861, your impression that some plugins are not yet
fully updated seems correct: for example, the "depack" plugin is using the
default "Main" category, but should be using the "OSGi" category.

So, I'm reopening FELIX-3861 in order to update missing "OSGi" plugin
categories later.

best regards;
/Pierre

On Tue, May 28, 2013 at 5:03 PM, Felix Meschberger wrote:

> Hi Pierre
>
> Am 28.05.2013 um 14:14 schrieb Pierre De Rop:
>
> > Just to notice that the
> > FELIX-3861issue is
> > still opened, and also present is the webconsole changelog.txt.
>
> Yes, I was under the impression, that the other plugins involved in the
> issue have not been adapted yet. But it looks they are, so I resolved the
> issue now.
>
> Regards
> Felix

[jira] [Commented] (FELIX-4088) NPE from SCR service unregistration

[Timothy Ward (JIRA)]

[ 
https://issues.apache.org/jira/browse/FELIX-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673330#comment-13673330
 ] 

Timothy Ward commented on FELIX-4088:
-

Hi [~djencks] - I have run the scenario again with a local build of the latest 
SCR code and I'm no longer seeing errors. Previously they were occurring about 
75% of the time, and I've run through 10 times since the update. This obviously 
doesn't guarantee that there isn't another race condition in the framework, but 
the fix you added has definitely improved things.

> NPE from SCR service unregistration
> ---
>
> Key: FELIX-4088
> URL: https://issues.apache.org/jira/browse/FELIX-4088
> Project: Felix
>  Issue Type: Bug
>  Components: Configuration Admin, Declarative Services (SCR), 
> Framework
>Affects Versions: framework-4.2.0,  configadmin-1.2.8,  scr-1.6.0
> Environment: MacOSX 8 processors
>Reporter: Timothy Ward
>
> When uninstalling a set of bundles I get the following exception.
> ERROR: Bundle com.paremus.dosgi.topologymanager [101] EventDispatcher: Error 
> during dispatch. (java.lang.NullPointerException)
> java.lang.NullPointerException
>   at org.apache.felix.framework.util.Util.getWire(Util.java:335)
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl$ServiceReferenceImpl.isAssignableTo(ServiceRegistrationImpl.java:493)
>   at 
> org.apache.felix.framework.util.Util.isServiceAssignable(Util.java:280)
>   at 
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:916)
>   at 
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)
>   at 
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)
>   at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4401)
>   at org.apache.felix.framework.Felix.access$000(Felix.java:74)
>   at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:390)
>   at 
> org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:151)
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:127)
>   at 
> com.paremus.frameworkintercept.DelegatingServiceRegistration.unregister(DelegatingServiceRegistration.java:37)
>   at 
> org.apache.felix.scr.impl.manager.AbstractComponentManager.unregisterComponentService(AbstractComponentManager.java:470)
>   at 
> org.apache.felix.scr.impl.manager.AbstractComponentManager$Satisfied.deactivate(AbstractComponentManager.java:1074)
>   at 
> org.apache.felix.scr.impl.manager.AbstractComponentManager.deactivateInternal(AbstractComponentManager.java:338)
>   at 
> org.apache.felix.scr.impl.manager.ImmediateComponentManager.reconfigure(ImmediateComponentManager.java:414)
>   at 
> org.apache.felix.scr.impl.config.ConfiguredComponentHolder.configurationDeleted(ConfiguredComponentHolder.java:152)
>   at 
> org.apache.felix.scr.impl.config.ConfigurationComponentRegistry.configurationEvent(ConfigurationComponentRegistry.java:247)
>   at 
> org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.run(ConfigurationManager.java:1832)
>   at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104)
>   at java.lang.Thread.run(Thread.java:722)
> ERROR: Bundle org.cauldron.newton.management.monitor [85] EventDispatcher: 
> Error during dispatch. (java.lang.NullPointerException)
> java.lang.NullPointerException
>   at org.apache.felix.framework.util.Util.getWire(Util.java:335)
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl$ServiceReferenceImpl.isAssignableTo(ServiceRegistrationImpl.java:493)
>   at 
> org.apache.felix.framework.util.Util.isServiceAssignable(Util.java:280)
>   at 
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:916)
>   at 
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)
>   at 
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)
>   at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4401)
>   at org.apache.felix.framework.Felix.access$000(Felix.java:74)
>   at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:390)
>   at 
> org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:151)
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:127)
>   at 
> com.paremus.frameworkintercept.DelegatingServiceRegistration.unregister(DelegatingServiceRegistration.java:37)
>   at 
> org.apache.felix.scr.impl.manager.AbstractComponentManager.unregister

[jira] [Resolved] (FELIX-4096) NPE when retrieve required and missing handler on a disposed factory

[Clement Escoffier (JIRA)]

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

Clement Escoffier resolved FELIX-4096.
--

Resolution: Fixed

Fixed in trunk

> NPE when retrieve required and missing handler on a disposed factory
> 
>
> Key: FELIX-4096
> URL: https://issues.apache.org/jira/browse/FELIX-4096
> Project: Felix
>  Issue Type: Bug
>  Components: iPOJO
>Affects Versions: ipojo-runtime-1.10
>Reporter: Clement Escoffier
>Assignee: Clement Escoffier
> Fix For: ipojo-runtime-1.10.1
>
>
> When the factory is stopped, the required handler list is set to null 
> avoiding retrieving the required handlers without getting an NPE.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FELIX-4100) Allow filter expression for which HttpService the whiteboard binds to

[Mike Wilson (JIRA)]

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

Mike Wilson updated FELIX-4100:
---

Description: 
Consider an OSGi system running the Felix HTTP whiteboard service and multiple 
HttpServices.

Currently it is not possible to control which HttpService the Felix whiteboard 
binds to for registering servlets and we get random behaviour. It would be 
natural to provide a configuration setting for the whiteboard that allows to 
specify a standard OSGi filter. 
This filter could then be used when calling superclass constructors from 
org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker.

It might also be appropriate to integrate the configuration setting with the 
standard ConfigurationAdmin service (this may deserve its own JIRA ticket 
though).

  was:
Consider an OSGi runtime with multiple running HttpServices.

Currently it is not possible to control which HttpService the Felix whiteboard 
binds to for registering servlets and we get random behaviour. It would be 
natural to provide a configuration setting for the whiteboard that allows to 
specify a standard OSGi filter. 
This filter could then be used when calling superclass constructors from 
org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker.

It might also be appropriate to integrate the configuration setting with the 
standard ConfigurationAdmin service (this may deserve its own JIRA ticket 
though).


> Allow filter expression for which HttpService the whiteboard binds to
> -
>
> Key: FELIX-4100
> URL: https://issues.apache.org/jira/browse/FELIX-4100
> Project: Felix
>  Issue Type: Improvement
>  Components: HTTP Service
>Affects Versions: http-2.2.0
>Reporter: Mike Wilson
>
> Consider an OSGi system running the Felix HTTP whiteboard service and 
> multiple HttpServices.
> Currently it is not possible to control which HttpService the Felix 
> whiteboard binds to for registering servlets and we get random behaviour. It 
> would be natural to provide a configuration setting for the whiteboard that 
> allows to specify a standard OSGi filter. 
> This filter could then be used when calling superclass constructors from 
> org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker.
> It might also be appropriate to integrate the configuration setting with the 
> standard ConfigurationAdmin service (this may deserve its own JIRA ticket 
> though).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FELIX-4100) Allow filter expression for which HttpService the whiteboard binds to

[Mike Wilson (JIRA)]

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

Mike Wilson updated FELIX-4100:
---

Description: 
Consider an OSGi system running the Felix HTTP whiteboard service and multiple 
HttpServices.

Currently it is not possible to control which HttpService the Felix whiteboard 
binds to for registering servlets. We get random binding behaviour. It would be 
natural to provide a configuration setting for the whiteboard that allows to 
specify a standard OSGi filter to refer to the desired HttpService.
This filter could then be used when calling superclass constructors from 
org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker.

It might also be appropriate to integrate the configuration setting with the 
standard ConfigurationAdmin service (this may deserve its own JIRA ticket 
though).

  was:
Consider an OSGi system running the Felix HTTP whiteboard service and multiple 
HttpServices.

Currently it is not possible to control which HttpService the Felix whiteboard 
binds to for registering servlets and we get random behaviour. It would be 
natural to provide a configuration setting for the whiteboard that allows to 
specify a standard OSGi filter. 
This filter could then be used when calling superclass constructors from 
org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker.

It might also be appropriate to integrate the configuration setting with the 
standard ConfigurationAdmin service (this may deserve its own JIRA ticket 
though).


> Allow filter expression for which HttpService the whiteboard binds to
> -
>
> Key: FELIX-4100
> URL: https://issues.apache.org/jira/browse/FELIX-4100
> Project: Felix
>  Issue Type: Improvement
>  Components: HTTP Service
>Affects Versions: http-2.2.0
>Reporter: Mike Wilson
>
> Consider an OSGi system running the Felix HTTP whiteboard service and 
> multiple HttpServices.
> Currently it is not possible to control which HttpService the Felix 
> whiteboard binds to for registering servlets. We get random binding 
> behaviour. It would be natural to provide a configuration setting for the 
> whiteboard that allows to specify a standard OSGi filter to refer to the 
> desired HttpService.
> This filter could then be used when calling superclass constructors from 
> org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker.
> It might also be appropriate to integrate the configuration setting with the 
> standard ConfigurationAdmin service (this may deserve its own JIRA ticket 
> though).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FELIX-4100) Allow filter expression for which HttpService the whiteboard binds to

[Mike Wilson (JIRA)]

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

Mike Wilson updated FELIX-4100:
---

Description: 
Consider an OSGi runtime with multiple running HttpServices.

Currently it is not possible to control which HttpService the Felix whiteboard 
binds to for registering servlets and we get random behaviour. It would be 
natural to provide a configuration setting for the whiteboard that allows to 
specify a standard OSGi filter. 
This filter could then be used when calling superclass constructors from 
org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker.

It might also be appropriate to integrate the configuration setting with the 
standard ConfigurationAdmin service (this may deserve its own JIRA ticket 
though).

  was:
Consider an OSGi runtime with multiple running HttpServices.

Currently it is not possible to control which HttpService the Felix whiteboard 
binds to for registering servlets and we get random behaviour. It would be 
natural to provide a configuration setting for the whiteboard that allows to 
specify a standard OSGi filter. This filter could then be used when calling 
superclass constructors from 
{code}
org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker
{code}

It might also be appropriate to integrate the configuration setting with the 
standard ConfigurationAdmin service (this may deserve its own JIRA ticket 
though).


> Allow filter expression for which HttpService the whiteboard binds to
> -
>
> Key: FELIX-4100
> URL: https://issues.apache.org/jira/browse/FELIX-4100
> Project: Felix
>  Issue Type: Improvement
>  Components: HTTP Service
>Affects Versions: http-2.2.0
>Reporter: Mike Wilson
>
> Consider an OSGi runtime with multiple running HttpServices.
> Currently it is not possible to control which HttpService the Felix 
> whiteboard binds to for registering servlets and we get random behaviour. It 
> would be natural to provide a configuration setting for the whiteboard that 
> allows to specify a standard OSGi filter. 
> This filter could then be used when calling superclass constructors from 
> org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker.
> It might also be appropriate to integrate the configuration setting with the 
> standard ConfigurationAdmin service (this may deserve its own JIRA ticket 
> though).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (FELIX-4100) Allow filter expression for which HttpService the whiteboard binds to

[Mike Wilson (JIRA)]

Mike Wilson created FELIX-4100:
--

 Summary: Allow filter expression for which HttpService the 
whiteboard binds to
 Key: FELIX-4100
 URL: https://issues.apache.org/jira/browse/FELIX-4100
 Project: Felix
  Issue Type: Improvement
  Components: HTTP Service
Affects Versions: http-2.2.0
Reporter: Mike Wilson


Consider an OSGi runtime with multiple running HttpServices.

Currently it is not possible to control which HttpService the Felix whiteboard 
binds to for registering servlets and we get random behaviour. It would be 
natural to provide a configuration setting for the whiteboard that allows to 
specify a standard OSGi filter. This filter could then be used when calling 
superclass constructors from 
{code}
org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker
{code}

It might also be appropriate to integrate the configuration setting with the 
standard ConfigurationAdmin service (this may deserve its own JIRA ticket 
though).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (FELIX-4099) Add support for negations in the multi property filter index

[Xander Uiterlinden (JIRA)]

Xander Uiterlinden created FELIX-4099:
-

 Summary: Add support for negations in the multi property filter 
index
 Key: FELIX-4099
 URL: https://issues.apache.org/jira/browse/FELIX-4099
 Project: Felix
  Issue Type: Wish
  Components: Dependency Manager
Reporter: Xander Uiterlinden
Assignee: Xander Uiterlinden


Currently the multi property exact filter does only support a simple 
comparison, but does not support negations, e.g. (&(a=x)(!(b=y))). It would be 
nice if support for negations could be added.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (FELIX-4099) Add support for negations in the multi property filter index

[Xander Uiterlinden (JIRA)]

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

Xander Uiterlinden resolved FELIX-4099.
---

Resolution: Fixed

Rewrote the multi property exact filter implementation and added negation 
support.

> Add support for negations in the multi property filter index
> 
>
> Key: FELIX-4099
> URL: https://issues.apache.org/jira/browse/FELIX-4099
> Project: Felix
>  Issue Type: Wish
>  Components: Dependency Manager
>Reporter: Xander Uiterlinden
>Assignee: Xander Uiterlinden
>
> Currently the multi property exact filter does only support a simple 
> comparison, but does not support negations, e.g. (&(a=x)(!(b=y))). It would 
> be nice if support for negations could be added.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (FELIX-4098) Aspect swap sometimes invokes the callbacks in the wrong order in a multithreaded application.

[Xander Uiterlinden (JIRA)]

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

Xander Uiterlinden resolved FELIX-4098.
---

Resolution: Fixed

Discovered the swap calculation and invocation also had some other issues. 
Rewrote this method and added synchronization for the callback method 
invocation using a guarded block.

> Aspect swap sometimes invokes the callbacks in the wrong order in a 
> multithreaded application.
> --
>
> Key: FELIX-4098
> URL: https://issues.apache.org/jira/browse/FELIX-4098
> Project: Felix
>  Issue Type: Improvement
>  Components: Dependency Manager
>Reporter: Xander Uiterlinden
>Assignee: Xander Uiterlinden
>Priority: Critical
>
> In a multithreaded application the swap callback invocations sometimes 
> overtake each other which causes in callbacks being invoked in the wrong 
> order.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Work started] (FELIX-4098) Aspect swap sometimes invokes the callbacks in the wrong order in a multithreaded application.

[Xander Uiterlinden (JIRA)]

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

Work on FELIX-4098 started by Xander Uiterlinden.

> Aspect swap sometimes invokes the callbacks in the wrong order in a 
> multithreaded application.
> --
>
> Key: FELIX-4098
> URL: https://issues.apache.org/jira/browse/FELIX-4098
> Project: Felix
>  Issue Type: Improvement
>  Components: Dependency Manager
>Reporter: Xander Uiterlinden
>Assignee: Xander Uiterlinden
>Priority: Critical
>
> In a multithreaded application the swap callback invocations sometimes 
> overtake each other which causes in callbacks being invoked in the wrong 
> order.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (FELIX-4098) Aspect swap sometimes invokes te callbacks in the wrong order in a multithreaded application.

[Xander Uiterlinden (JIRA)]

Xander Uiterlinden created FELIX-4098:
-

 Summary: Aspect swap sometimes invokes te callbacks in the wrong 
order in a multithreaded application.
 Key: FELIX-4098
 URL: https://issues.apache.org/jira/browse/FELIX-4098
 Project: Felix
  Issue Type: Improvement
  Components: Dependency Manager
Reporter: Xander Uiterlinden
Assignee: Xander Uiterlinden
Priority: Critical


In a multithreaded application the swap callback invocations sometimes overtake 
each other which causes in callbacks being invoked in the wrong order.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [VOTE] Release DeploymentAdmin 0.9.4 and AutoConf Processor 0.1.4

[Jan Willem Janssen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 5/31/13 3:49 PM, Marcel Offermans wrote:
> Please vote to approve this release:
> 
> [x] +1 Approve the release [ ] -1 Veto the release (please provide
> specific comments)
> 
> This vote will be open for 72 hours.

+1 (non-binding)

- -- 
Met vriendelijke groeten | Kind regards

Jan Willem Janssen | Software Architect
+31 631 765 814

/My world is revolving around PulseOn and Amdatu/

Luminis Technologies B.V.
J.C. Wilslaan 29
7313 HK   Apeldoorn
+31 88 586 46 30

http://www.luminis-technologies.com
http://www.luminis.eu

KvK (CoC) 09 16 28 93
BTW (VAT) NL8169.78.566.B.01
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRrIYfAAoJEKF/mP2eHDc4zvcP+wZcWj7yV/yPaNrEPZikaqns
7x/hMQiO0UA4oLs/MiRXnDBEOaHH60ahSZ4qDEabIpSX6rXW01eAmG3Uf44lAXRu
R/v/Sh4rnl4j1iEoXiJC4yYSnEm6cwCOVLphcXBABciTpO3nU3GltMGMOuPeSVOb
mqSMQKn+ZbMgXDY725AK6dV13pSSk40BGN8WikVHBTWGiG8Qsdux0usbCr8XQgYP
0AgixoTOtd2U/hf84sVYirk5l2OqqEShDXIaQcmpM34NQI/DOcBOfPYHzUGoDb5O
rukNFCsmbxI/0pducN49UmlkY8DcP+wDJwESaWGAYJJsWMcqk3EVV2Ug07TpL2gb
dNOwDRFiLlnMOh7h+QffVFdens21vADttuRYfhmc0D6WQpGZNBwZIewBT33gllMj
7/LH7Ml4oqeWKWPxj8Gg+GFSBEXwO1ODU2stAD/kX0SBlPXpkIkTxPrCGo9syJpt
bHuvV4Q8WVcGhAQwz2XNf11fUozzFW7A0besPkWSB+raiHstWvbAIo1GdbqJ170d
9unw6gQlfCn47nZ+PDGT2CcsPc17FMg1m6N/4/RJ6jkYV7fDuEkIrq6qnC8rIDc9
FwRBLxFLh7vJS1rfIf731iA53mUxr5oxamAX7QqNQ5fiwc1H3FkmgQwnRv657i4v
1KujTwEA783k7KI5xVhB
=PKgh
-END PGP SIGNATURE-

[jira] [Updated] (FELIX-4098) Aspect swap sometimes invokes the callbacks in the wrong order in a multithreaded application.

[Xander Uiterlinden (JIRA)]

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

Xander Uiterlinden updated FELIX-4098:
--

Summary: Aspect swap sometimes invokes the callbacks in the wrong order in 
a multithreaded application.  (was: Aspect swap sometimes invokes te callbacks 
in the wrong order in a multithreaded application.)

> Aspect swap sometimes invokes the callbacks in the wrong order in a 
> multithreaded application.
> --
>
> Key: FELIX-4098
> URL: https://issues.apache.org/jira/browse/FELIX-4098
> Project: Felix
>  Issue Type: Improvement
>  Components: Dependency Manager
>Reporter: Xander Uiterlinden
>Assignee: Xander Uiterlinden
>Priority: Critical
>
> In a multithreaded application the swap callback invocations sometimes 
> overtake each other which causes in callbacks being invoked in the wrong 
> order.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Work stopped] (FELIX-4097) Allow debug logging for specific instances of service dependencies to debug wiring issues.

[Xander Uiterlinden (JIRA)]

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

Work on FELIX-4097 stopped by Xander Uiterlinden.

> Allow debug logging for specific instances of service dependencies to debug 
> wiring issues.
> --
>
> Key: FELIX-4097
> URL: https://issues.apache.org/jira/browse/FELIX-4097
> Project: Felix
>  Issue Type: Improvement
>  Components: Dependency Manager
>Affects Versions: dependencymanager-3.1.0
>Reporter: Xander Uiterlinden
>Assignee: Xander Uiterlinden
>Priority: Minor
>
> Sometimes it can really help when a specific servicedependency can be tracked 
> when debugging wiring / dependency injection issues so it would be very 
> helpful if a servicedependency can be configured with a debug parameter which 
> a: enables debug logging for this service dependency, b. allows for a 
> conditional breakpoint to step into the methods of this instance only.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Work started] (FELIX-4097) Allow debug logging for specific instances of service dependencies to debug wiring issues.

[Xander Uiterlinden (JIRA)]

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

Work on FELIX-4097 started by Xander Uiterlinden.

> Allow debug logging for specific instances of service dependencies to debug 
> wiring issues.
> --
>
> Key: FELIX-4097
> URL: https://issues.apache.org/jira/browse/FELIX-4097
> Project: Felix
>  Issue Type: Improvement
>  Components: Dependency Manager
>Affects Versions: dependencymanager-3.1.0
>Reporter: Xander Uiterlinden
>Assignee: Xander Uiterlinden
>Priority: Minor
>
> Sometimes it can really help when a specific servicedependency can be tracked 
> when debugging wiring / dependency injection issues so it would be very 
> helpful if a servicedependency can be configured with a debug parameter which 
> a: enables debug logging for this service dependency, b. allows for a 
> conditional breakpoint to step into the methods of this instance only.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (FELIX-4097) Allow debug logging for specific instances of service dependencies to debug wiring issues.

[Xander Uiterlinden (JIRA)]

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

Xander Uiterlinden resolved FELIX-4097.
---

Resolution: Fixed

added setDebug(String identifier) to ServiceDependency allowing to track a 
single service dependency by a self specified identifier. This identifier is 
included in the debug logging and can be used to set conditional breakpoints.

> Allow debug logging for specific instances of service dependencies to debug 
> wiring issues.
> --
>
> Key: FELIX-4097
> URL: https://issues.apache.org/jira/browse/FELIX-4097
> Project: Felix
>  Issue Type: Improvement
>  Components: Dependency Manager
>Affects Versions: dependencymanager-3.1.0
>Reporter: Xander Uiterlinden
>Assignee: Xander Uiterlinden
>Priority: Minor
>
> Sometimes it can really help when a specific servicedependency can be tracked 
> when debugging wiring / dependency injection issues so it would be very 
> helpful if a servicedependency can be configured with a debug parameter which 
> a: enables debug logging for this service dependency, b. allows for a 
> conditional breakpoint to step into the methods of this instance only.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (FELIX-4097) Allow debug logging for specific instances of service dependencies to debug wiring issues.

[Xander Uiterlinden (JIRA)]

Xander Uiterlinden created FELIX-4097:
-

 Summary: Allow debug logging for specific instances of service 
dependencies to debug wiring issues.
 Key: FELIX-4097
 URL: https://issues.apache.org/jira/browse/FELIX-4097
 Project: Felix
  Issue Type: Improvement
  Components: Dependency Manager
Affects Versions: dependencymanager-3.1.0
Reporter: Xander Uiterlinden
Assignee: Xander Uiterlinden
Priority: Minor


Sometimes it can really help when a specific servicedependency can be tracked 
when debugging wiring / dependency injection issues so it would be very helpful 
if a servicedependency can be configured with a debug parameter which a: 
enables debug logging for this service dependency, b. allows for a conditional 
breakpoint to step into the methods of this instance only.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (FELIX-4014) handleAspectAwareRemoved in ServiceDependencyImpl can cause a possible deadlock

[Xander Uiterlinden (JIRA)]

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

Xander Uiterlinden resolved FELIX-4014.
---

Resolution: Fixed

fixed by moving the callback outside of the synchronized block.

> handleAspectAwareRemoved in ServiceDependencyImpl can cause a possible 
> deadlock
> ---
>
> Key: FELIX-4014
> URL: https://issues.apache.org/jira/browse/FELIX-4014
> Project: Felix
>  Issue Type: Bug
>  Components: Dependency Manager
>Reporter: Xander Uiterlinden
>Assignee: Xander Uiterlinden
>
> the handleAspectAwareRemoved invokes a callback method within a 
> synchronization block. Since we don't know what will be going there this can 
> cause (and in our case does cause) concurrency issues.
> The fix would be to move the invoke out of the sync block.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Work started] (FELIX-4014) handleAspectAwareRemoved in ServiceDependencyImpl can cause a possible deadlock

[Xander Uiterlinden (JIRA)]

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

Work on FELIX-4014 started by Xander Uiterlinden.

> handleAspectAwareRemoved in ServiceDependencyImpl can cause a possible 
> deadlock
> ---
>
> Key: FELIX-4014
> URL: https://issues.apache.org/jira/browse/FELIX-4014
> Project: Felix
>  Issue Type: Bug
>  Components: Dependency Manager
>Reporter: Xander Uiterlinden
>Assignee: Xander Uiterlinden
>
> the handleAspectAwareRemoved invokes a callback method within a 
> synchronization block. Since we don't know what will be going there this can 
> cause (and in our case does cause) concurrency issues.
> The fix would be to move the invoke out of the sync block.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [VOTE] SCR Tooling Release

[Carsten Ziegeler]

+1

Carsten


2013/6/3 Carsten Ziegeler 

> Hi,
>
> we have a few fixes for our SCR tooling:
>
> SCR Generator 1.7.0
> https://issues.apache.org/jira/browse/FELIX/fixforversion/12324365
>
> Maven SCR Plugin 1.13.0
> https://issues.apache.org/jira/browse/FELIX/fixforversion/12324364
>
> SCR Ant Task 1.7.0
> https://issues.apache.org/jira/browse/FELIX/fixforversion/12324366
>
> SCR Annotations 1.9.4
> https://issues.apache.org/jira/browse/FELIX/fixforversion/12324363
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachefelix-054/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 054 /tmp/felix-staging
>
>
> Please vote to approve this release:
>
>  [ ] +1 Approve the release
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...
>
> This vote will be open for 72 hours.
>
> Regards
> Carsten
> --
> Carsten Ziegeler
> cziege...@apache.org
>



-- 
Carsten Ziegeler
cziege...@apache.org

DP WebConsole suggestion (Was: Re: [VOTE] Release DeploymentAdmin 0.9.4 and AutoConf Processor 0.1.4)

[Marcel Offermans]

On Jun 3, 2013, at 12:32 PM, Pierre De Rop  wrote:

> A minor remark regarding the DP webconsole plugin (not concerned by this
> candidate release), I see that DP is located in the "Main" tab instead of
> the "OSGi" tab.
> May be I should open a jira issue for moving DP in the "OSGi" webconsole
> tab section ?

That makes sense, Pierre, please do open an issue for that!

Greetings, Marcel

Re: [VOTE] Release DeploymentAdmin 0.9.4 and AutoConf Processor 0.1.4

[Pierre De Rop]

Hi Marcel;

+1

A minor remark regarding the DP webconsole plugin (not concerned by this
candidate release), I see that DP is located in the "Main" tab instead of
the "OSGi" tab.
May be I should open a jira issue for moving DP in the "OSGi" webconsole
tab section ?

best regards;
/Pierre

On Fri, May 31, 2013 at 3:49 PM, Marcel Offermans <
marcel.offerm...@luminis.nl> wrote:

> Hi all,
>
> After cancelling the previous release, I've fixed the issue and I'd like
> to announce the new vote for two Felix bundles. These are the changelogs:
>
> DeploymentAdmin Release 0.9.4
> -
>
> FELIX-3336 Exceptions related to the pipe used in deployment admin
> FELIX-3272 Add property to allow foreign resource processors
> FELIX-3515 DeploymentAdmin triggers IOException on install
> FELIX-1307 Log situation in DeploymentAdmin impl very unclear
> FELIX-3270 Deployment admin incorrectly takes snapshots of bundle data
> areas
> FELIX-3526 DeploymentAdmin fails on windows due to unclosed iostreams
> FELIX-1828 Mistake in code of the class UpdateCommand
> FELIX-1829 Method AbstractDeploymentPackage.getBundle(...) throws
> NullPointerException
> FELIX-3678 org.apache.felix.deploymentadmin imports wrong version of
> org.osgi.service.deploymentadmin
> FELIX-3139 Implement uninstall() for deployment admin.
>
> AutoConf Processor Release 0.1.4
> -
>
> FELIX-3243 Autoconf does not recognize non-local non-factory OCDs
> FELIX-3245 Autoconf handles metatype 1.1 cardinalty wrong
> FELIX-3400 Nullpointer in autoconfprocessor for invalid metatype files
>
>
> There are still some outstanding issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20component%20%3D%20%22Deployment%20Admin%22%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachefelix-042/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 042 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>
> Have a nice weekend!
>
> Greetings, Marcel
>
>

Re: [VOTE] Release DeploymentAdmin 0.9.4 and AutoConf Processor 0.1.4

[Carsten Ziegeler]

+1

Carsten


2013/6/3 Bram de Kruijff 

> On Fri, May 31, 2013 at 3:49 PM, Marcel Offermans
>  wrote:
> > Hi all,
> >
> > After cancelling the previous release, I've fixed the issue and I'd like
> to announce the new vote for two Felix bundles. These are the changelogs:
> >
> > DeploymentAdmin Release 0.9.4
> > -
> >
> > FELIX-3336 Exceptions related to the pipe used in deployment admin
> > FELIX-3272 Add property to allow foreign resource processors
> > FELIX-3515 DeploymentAdmin triggers IOException on install
> > FELIX-1307 Log situation in DeploymentAdmin impl very unclear
> > FELIX-3270 Deployment admin incorrectly takes snapshots of bundle data
> areas
> > FELIX-3526 DeploymentAdmin fails on windows due to unclosed iostreams
> > FELIX-1828 Mistake in code of the class UpdateCommand
> > FELIX-1829 Method AbstractDeploymentPackage.getBundle(...) throws
> NullPointerException
> > FELIX-3678 org.apache.felix.deploymentadmin imports wrong version of
> org.osgi.service.deploymentadmin
> > FELIX-3139 Implement uninstall() for deployment admin.
> >
> > AutoConf Processor Release 0.1.4
> > -
> >
> > FELIX-3243 Autoconf does not recognize non-local non-factory OCDs
> > FELIX-3245 Autoconf handles metatype 1.1 cardinalty wrong
> > FELIX-3400 Nullpointer in autoconfprocessor for invalid metatype files
> >
> >
> > There are still some outstanding issues:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20component%20%3D%20%22Deployment%20Admin%22%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachefelix-042/
> >
> > You can use this UNIX script to download the release and verify the
> signatures:
> > http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 042 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
>
> +1 (non-binding)
>
> Artifacts look good and I found no regression during initial testing.
>
> Regards,
> Bram
>
>
>
> > This vote will be open for 72 hours.
> >
> > Have a nice weekend!
> >
> > Greetings, Marcel
> >
>



-- 
Carsten Ziegeler
cziege...@apache.org

[VOTE] SCR Tooling Release

[Carsten Ziegeler]

Hi,

we have a few fixes for our SCR tooling:

SCR Generator 1.7.0
https://issues.apache.org/jira/browse/FELIX/fixforversion/12324365

Maven SCR Plugin 1.13.0
https://issues.apache.org/jira/browse/FELIX/fixforversion/12324364

SCR Ant Task 1.7.0
https://issues.apache.org/jira/browse/FELIX/fixforversion/12324366

SCR Annotations 1.9.4
https://issues.apache.org/jira/browse/FELIX/fixforversion/12324363

Staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-054/

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 054 /tmp/felix-staging


Please vote to approve this release:

 [ ] +1 Approve the release
 [ ]  0 Don't care
 [ ] -1 Don't release, because ...

This vote will be open for 72 hours.

Regards
Carsten
-- 
Carsten Ziegeler
cziege...@apache.org

[jira] [Updated] (FELIX-4063) Avoid warnings when using @SlingServlet and @SlingFilter annotations

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler updated FELIX-4063:


Fix Version/s: scr annotations 1.9.4

> Avoid warnings when using @SlingServlet and @SlingFilter annotations
> 
>
> Key: FELIX-4063
> URL: https://issues.apache.org/jira/browse/FELIX-4063
> Project: Felix
>  Issue Type: Bug
>  Components: Maven SCR Plugin
>Affects Versions: scr annotations 1.9.2
>Reporter: Julian Sedding
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: scr annotations 1.9.4
>
> Attachments: FELIX-4063.patch
>
>
> FELIX-4033 introduced build-time warning messages for private properties 
> defined for components with metatype = false.
> The @SlingServlet and @SlingFilter annotations set several properties to be 
> private, thus causing warnings like the following to be reported if metatype 
> = false (the default value).
> [WARNING] /path/TheServlet.java [0:0]: Property sling.servlet.methods in 
> class TheServlet is set as private. This is redundant as no metatype will be 
> generated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FELIX-4058) PropertyType password has a wrong type (passwort)

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler updated FELIX-4058:


Summary: PropertyType password has a wrong type (passwort)  (was: 
PropertyType password has a type (passwort))

> PropertyType password has a wrong type (passwort)
> -
>
> Key: FELIX-4058
> URL: https://issues.apache.org/jira/browse/FELIX-4058
> Project: Felix
>  Issue Type: Bug
>  Components: Maven SCR Plugin
>Affects Versions: maven-scr-plugin-1.11.0, maven-scr-plugin-1.12.0, scr 
> ant task 1.5.0, scr ant task 1.6.0, scr generator 1.5.0, scr generator 1.6.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: maven-scr-plugin 1.13.0, scr ant task 1.7.0, scr 
> generator 1.7.0
>
>
> The enum for the password has a type which leads to an error if is this type 
> is used in an annotation

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (FELIX-4096) NPE when retrieve required and missing handler on a disposed factory

[Clement Escoffier (JIRA)]

Clement Escoffier created FELIX-4096:


 Summary: NPE when retrieve required and missing handler on a 
disposed factory
 Key: FELIX-4096
 URL: https://issues.apache.org/jira/browse/FELIX-4096
 Project: Felix
  Issue Type: Bug
  Components: iPOJO
Affects Versions: ipojo-runtime-1.10
Reporter: Clement Escoffier
Assignee: Clement Escoffier
 Fix For: ipojo-runtime-1.10.1


When the factory is stopped, the required handler list is set to null avoiding 
retrieving the required handlers without getting an NPE.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [VOTE] Release DeploymentAdmin 0.9.4 and AutoConf Processor 0.1.4

[Bram de Kruijff]

On Fri, May 31, 2013 at 3:49 PM, Marcel Offermans
 wrote:
> Hi all,
>
> After cancelling the previous release, I've fixed the issue and I'd like to 
> announce the new vote for two Felix bundles. These are the changelogs:
>
> DeploymentAdmin Release 0.9.4
> -
>
> FELIX-3336 Exceptions related to the pipe used in deployment admin
> FELIX-3272 Add property to allow foreign resource processors
> FELIX-3515 DeploymentAdmin triggers IOException on install
> FELIX-1307 Log situation in DeploymentAdmin impl very unclear
> FELIX-3270 Deployment admin incorrectly takes snapshots of bundle data areas
> FELIX-3526 DeploymentAdmin fails on windows due to unclosed iostreams
> FELIX-1828 Mistake in code of the class UpdateCommand
> FELIX-1829 Method AbstractDeploymentPackage.getBundle(...) throws 
> NullPointerException
> FELIX-3678 org.apache.felix.deploymentadmin imports wrong version of 
> org.osgi.service.deploymentadmin
> FELIX-3139 Implement uninstall() for deployment admin.
>
> AutoConf Processor Release 0.1.4
> -
>
> FELIX-3243 Autoconf does not recognize non-local non-factory OCDs
> FELIX-3245 Autoconf handles metatype 1.1 cardinalty wrong
> FELIX-3400 Nullpointer in autoconfprocessor for invalid metatype files
>
>
> There are still some outstanding issues:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20component%20%3D%20%22Deployment%20Admin%22%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachefelix-042/
>
> You can use this UNIX script to download the release and verify the 
> signatures:
> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 042 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>

+1 (non-binding)

Artifacts look good and I found no regression during initial testing.

Regards,
Bram



> This vote will be open for 72 hours.
>
> Have a nice weekend!
>
> Greetings, Marcel
>