[jira] [Commented] (FELIX-6726) One reference can be unset more then once and will cause IllegalStateException in Framework

[ https://issues.apache.org/jira/browse/FELIX-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881611#comment-17881611 ] Tom Watson commented on FELIX-6726: --- {quote}to avoid the Exception in the first place,

[jira] [Updated] (FELIX-6726) One reference can be unset more then once and will cause IllegalStateException in Framework

[ https://issues.apache.org/jira/browse/FELIX-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6726: -- Component/s: Framework (was: Declarative Services (SCR)) > One reference can be un

[jira] [Commented] (FELIX-6726) One reference can be unset more then once and will cause IllegalStateException in Framework

[ https://issues.apache.org/jira/browse/FELIX-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881333#comment-17881333 ] Tom Watson commented on FELIX-6726: ---   {quote}Even calling it twice should not cause th

[jira] [Closed] (FELIX-6616) Dynamic greedy 1..1 references may activate with no reference service bound

[ https://issues.apache.org/jira/browse/FELIX-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6616. - > Dynamic greedy 1..1 references may activate with no reference service bound > -

[jira] [Closed] (FELIX-6463) Changing log levels for DS component getState and registration

[ https://issues.apache.org/jira/browse/FELIX-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6463. - > Changing log levels for DS component getState and registration > --

[jira] [Closed] (FELIX-6682) Felix SCR - 3 TestCases fail in OSGi TCK

[ https://issues.apache.org/jira/browse/FELIX-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6682. - > Felix SCR - 3 TestCases fail in OSGi TCK > - > > K

[jira] [Resolved] (FELIX-6699) [DS] Excessive ERROR logging when Overlap in Service-Component header between wildcard and non-wildcard locations

[ https://issues.apache.org/jira/browse/FELIX-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-6699. --- Resolution: Fixed > [DS] Excessive ERROR logging when Overlap in Service-Component header between >

[jira] [Assigned] (FELIX-6699) [DS] Excessive ERROR logging when Overlap in Service-Component header between wildcard and non-wildcard locations

[ https://issues.apache.org/jira/browse/FELIX-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson reassigned FELIX-6699: - Assignee: Tom Watson > [DS] Excessive ERROR logging when Overlap in Service-Component header bet

[jira] [Updated] (FELIX-6667) Reresoliving hosts or resolving new fragments does not invalidate meta-data cache for SCR

[ https://issues.apache.org/jira/browse/FELIX-6667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6667: -- Fix Version/s: scr-2.2.10 scr-2.2.8 > Reresoliving hosts or resolving new fragments

[jira] [Closed] (FELIX-6633) Dynamic references may miss events while causing deactivation

[ https://issues.apache.org/jira/browse/FELIX-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6633. - > Dynamic references may miss events while causing deactivation > ---

[jira] [Commented] (FELIX-6697) ServiceReference.isAssignableTo() allows any bundle to get access to unexported services from any other bundle

[ https://issues.apache.org/jira/browse/FELIX-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838210#comment-17838210 ] Tom Watson commented on FELIX-6697: --- {quote}Does it mean that a version 7 implementatio

[jira] [Commented] (FELIX-6697) ServiceReference.isAssignableTo() allows any bundle to get access to unexported services from any other bundle

[ https://issues.apache.org/jira/browse/FELIX-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838171#comment-17838171 ] Tom Watson commented on FELIX-6697: --- See [https://docs.osgi.org/specification/osgi.cor

[jira] [Updated] (FELIX-6682) Felix SCR - 3 TestCases fail in OSGi TCK

[ https://issues.apache.org/jira/browse/FELIX-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6682: -- Fix Version/s: scr-2.2.10 > Felix SCR - 3 TestCases fail in OSGi TCK > ---

[jira] [Updated] (FELIX-6463) Changing log levels for DS component getState and registration

[ https://issues.apache.org/jira/browse/FELIX-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6463: -- Fix Version/s: scr-2.2.10 > Changing log levels for DS component getState and registration > --

[jira] [Updated] (FELIX-6616) Dynamic greedy 1..1 references may activate with no reference service bound

[ https://issues.apache.org/jira/browse/FELIX-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6616: -- Fix Version/s: scr-2.2.10 > Dynamic greedy 1..1 references may activate with no reference service bound

[jira] [Updated] (FELIX-6633) Dynamic references may miss events while causing deactivation

[ https://issues.apache.org/jira/browse/FELIX-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6633: -- Fix Version/s: scr-2.2.10 > Dynamic references may miss events while causing deactivation > ---

[jira] [Resolved] (FELIX-6682) Felix SCR - 3 TestCases fail in OSGi TCK

[ https://issues.apache.org/jira/browse/FELIX-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-6682. --- Resolution: Fixed Fix has been merged. > Felix SCR - 3 TestCases fail in OSGi TCK > ---

[jira] [Updated] (FELIX-6682) Felix SCR - 3 TestCases fail in OSGi TCK

[ https://issues.apache.org/jira/browse/FELIX-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6682: -- Fix Version/s: scr-2.2.8 > Felix SCR - 3 TestCases fail in OSGi TCK >

[jira] [Commented] (FELIX-6682) Felix SCR - 3 TestCases fail in OSGi TCK

[ https://issues.apache.org/jira/browse/FELIX-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807871#comment-17807871 ] Tom Watson commented on FELIX-6682: --- Fix going with https://github.com/apache/felix-dev

[jira] [Commented] (FELIX-6682) Felix SCR - 3 TestCases fail in OSGi TCK

[ https://issues.apache.org/jira/browse/FELIX-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807861#comment-17807861 ] Tom Watson commented on FELIX-6682: --- See https://github.com/osgi/osgi/pull/657#issuecom

[jira] [Created] (FELIX-6667) Reresoliving hosts or resolving new fragments does not invalidate meta-data cache for SCR

Tom Watson created FELIX-6667: - Summary: Reresoliving hosts or resolving new fragments does not invalidate meta-data cache for SCR Key: FELIX-6667 URL: https://issues.apache.org/jira/browse/FELIX-6667 Pro

[jira] [Resolved] (FELIX-6633) Dynamic references may miss events while causing deactivation

[ https://issues.apache.org/jira/browse/FELIX-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-6633. --- Fix Version/s: scr-2.2.8 Assignee: Tom Watson Resolution: Fixed > Dynamic references

[jira] [Created] (FELIX-6633) Dynamic references may miss events while causing deactivation

Tom Watson created FELIX-6633: - Summary: Dynamic references may miss events while causing deactivation Key: FELIX-6633 URL: https://issues.apache.org/jira/browse/FELIX-6633 Project: Felix Issue

[jira] [Resolved] (FELIX-6616) Dynamic greedy 1..1 references may activate with no reference service bound

[ https://issues.apache.org/jira/browse/FELIX-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-6616. --- Resolution: Fixed > Dynamic greedy 1..1 references may activate with no reference service bound > ---

[jira] [Commented] (FELIX-6616) Dynamic greedy 1..1 references may activate with no reference service bound

[ https://issues.apache.org/jira/browse/FELIX-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756881#comment-17756881 ] Tom Watson commented on FELIX-6616: --- I merged https://github.com/apache/felix-dev/pull/

[jira] [Commented] (FELIX-6616) Dynamic greedy 1..1 references may activate with no reference service bound

[ https://issues.apache.org/jira/browse/FELIX-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743821#comment-17743821 ] Tom Watson commented on FELIX-6616: --- My particular case is using a dynamic, greedy refe

[jira] [Created] (FELIX-6616) Dynamic greedy 1..1 references may activate with no reference service bound

Tom Watson created FELIX-6616: - Summary: Dynamic greedy 1..1 references may activate with no reference service bound Key: FELIX-6616 URL: https://issues.apache.org/jira/browse/FELIX-6616 Project: Felix

[jira] [Commented] (FELIX-6048) Could not obtain lock

[ https://issues.apache.org/jira/browse/FELIX-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682701#comment-17682701 ] Tom Watson commented on FELIX-6048: --- Any chance you can try running with debug logging

[jira] [Commented] (FELIX-6589) update method with constructor injection does not work

[ https://issues.apache.org/jira/browse/FELIX-6589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682092#comment-17682092 ] Tom Watson commented on FELIX-6589: --- updated only applies to method injection: https:

[jira] [Commented] (FELIX-6589) update method with constructor injection does not work

[ https://issues.apache.org/jira/browse/FELIX-6589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681591#comment-17681591 ] Tom Watson commented on FELIX-6589: --- Seems a bit strange to specify updates for a stati

[jira] [Updated] (FELIX-6581) When using ds.global.extender the LogManager can leak objects when bundles stopped

[ https://issues.apache.org/jira/browse/FELIX-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6581: -- Fix Version/s: scr-2.2.6 (was: scr-2.2.4) > When using ds.global.extender the Lo

[jira] [Reopened] (FELIX-6581) When using ds.global.extender the LogManager can leak objects when bundles stopped

[ https://issues.apache.org/jira/browse/FELIX-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson reopened FELIX-6581: --- > When using ds.global.extender the LogManager can leak objects when bundles > stopped > ---

[jira] [Closed] (FELIX-6581) When using ds.global.extender the LogManager can leak objects when bundles stopped

[ https://issues.apache.org/jira/browse/FELIX-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6581. - Resolution: Fixed > When using ds.global.extender the LogManager can leak objects when bundles > stopped

[jira] [Closed] (FELIX-6581) When using ds.global.extender the LogManager can leak objects when bundles stopped

[ https://issues.apache.org/jira/browse/FELIX-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6581. - > When using ds.global.extender the LogManager can leak objects when bundles > stopped > ---

[jira] [Updated] (FELIX-6581) When using ds.global.extender the LogManager can leak objects when bundles stopped

[ https://issues.apache.org/jira/browse/FELIX-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6581: -- Fix Version/s: 2.2.4 > When using ds.global.extender the LogManager can leak objects when bundles > st

[jira] [Resolved] (FELIX-6581) When using ds.global.extender the LogManager can leak objects when bundles stopped

[ https://issues.apache.org/jira/browse/FELIX-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-6581. --- Fix Version/s: scr-2.2.4 (was: 2.2.4) Resolution: Fixed > When using ds

[jira] [Commented] (FELIX-6581) When using ds.global.extender the LogManager can leak objects when bundles stopped

[ https://issues.apache.org/jira/browse/FELIX-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678242#comment-17678242 ] Tom Watson commented on FELIX-6581: --- This was fixed in commit https://github.com/apach

[jira] [Created] (FELIX-6581) When using ds.global.extender the LogManager can leak objects when bundles stopped

Tom Watson created FELIX-6581: - Summary: When using ds.global.extender the LogManager can leak objects when bundles stopped Key: FELIX-6581 URL: https://issues.apache.org/jira/browse/FELIX-6581 Project: F

[jira] [Commented] (FELIX-6552) In case of class-cast exception, a component is still activated

[ https://issues.apache.org/jira/browse/FELIX-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573752#comment-17573752 ] Tom Watson commented on FELIX-6552: --- An error should have been logged with the LogServi

[jira] [Commented] (FELIX-6544) SRC backwards compatibility

[ https://issues.apache.org/jira/browse/FELIX-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558874#comment-17558874 ] Tom Watson commented on FELIX-6544: --- Perhaps a minor version bump would have been appro

[jira] [Commented] (FELIX-6525) org.apache.felix.http.servlet-api exports multiple versions with no uses

[ https://issues.apache.org/jira/browse/FELIX-6525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529440#comment-17529440 ] Tom Watson commented on FELIX-6525: --- Thanks [~cziegeler]. That is what I figured given

[jira] [Created] (FELIX-6525) org.apache.felix.http.servlet-api exports multiple versions with no uses

Tom Watson created FELIX-6525: - Summary: org.apache.felix.http.servlet-api exports multiple versions with no uses Key: FELIX-6525 URL: https://issues.apache.org/jira/browse/FELIX-6525 Project: Felix

[jira] [Commented] (FELIX-6521) Stop exporting org.osgi.service.component packages

[ https://issues.apache.org/jira/browse/FELIX-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527693#comment-17527693 ] Tom Watson commented on FELIX-6521: --- I verified Felix SCR still passes the TCK with thi

[jira] [Commented] (FELIX-5359) Remove usage of deprecated PackageAdmin

[ https://issues.apache.org/jira/browse/FELIX-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527691#comment-17527691 ] Tom Watson commented on FELIX-5359: --- I verified Felix SCR still passes the OSGi TCK wit

[jira] [Comment Edited] (FELIX-5359) Remove usage of deprecated PackageAdmin

[ https://issues.apache.org/jira/browse/FELIX-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526642#comment-17526642 ] Tom Watson edited comment on FELIX-5359 at 4/25/22 6:02 PM: I

[jira] [Resolved] (FELIX-6521) Stop exporting org.osgi.service.component packages

[ https://issues.apache.org/jira/browse/FELIX-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-6521. --- Fix Version/s: scr-2.2.2 Resolution: Fixed Fixed with PR https://github.com/apache/felix-dev/p

[jira] [Resolved] (FELIX-5359) Remove usage of deprecated PackageAdmin

[ https://issues.apache.org/jira/browse/FELIX-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-5359. --- Fix Version/s: scr-2.2.2 Resolution: Fixed > Remove usage of deprecated PackageAdmin > --

[jira] [Commented] (FELIX-5359) Remove usage of deprecated PackageAdmin

[ https://issues.apache.org/jira/browse/FELIX-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527525#comment-17527525 ] Tom Watson commented on FELIX-5359: --- This is fixed in commit 8ee58352065c94620af3e14dce

[jira] [Reopened] (FELIX-5359) Remove usage of deprecated PackageAdmin

[ https://issues.apache.org/jira/browse/FELIX-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson reopened FELIX-5359: --- Assignee: Tom Watson In noticed package admin imports again and spent some time looking at removing

[jira] [Commented] (FELIX-6521) Stop exporting org.osgi.service.component packages

[ https://issues.apache.org/jira/browse/FELIX-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526491#comment-17526491 ] Tom Watson commented on FELIX-6521: --- I'm suggesting we follow the most recent guideline

[jira] [Commented] (FELIX-6521) Stop exporting org.osgi.service.component packages

[ https://issues.apache.org/jira/browse/FELIX-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524284#comment-17524284 ] Tom Watson commented on FELIX-6521: --- Yes, all subpackages of org.osgi.service.component

[jira] [Updated] (FELIX-6521) Stop exporting org.osgi.service.component packages

[ https://issues.apache.org/jira/browse/FELIX-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6521: -- Summary: Stop exporting org.osgi.service.component packages (was: Stop exporting org.osgi.service.comp

[jira] [Created] (FELIX-6521) Stop exporting org.osgi.service.component package

Tom Watson created FELIX-6521: - Summary: Stop exporting org.osgi.service.component package Key: FELIX-6521 URL: https://issues.apache.org/jira/browse/FELIX-6521 Project: Felix Issue Type: Improve

[jira] [Resolved] (FELIX-6511) Felix SCR ComponentRegistry leaves Timer thread running on deactivation.

[ https://issues.apache.org/jira/browse/FELIX-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-6511. --- Assignee: Tom Watson Resolution: Fixed > Felix SCR ComponentRegistry leaves Timer thread runnin

[jira] [Updated] (FELIX-6511) Felix SCR ComponentRegistry leaves Timer thread running on deactivation.

[ https://issues.apache.org/jira/browse/FELIX-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6511: -- Fix Version/s: scr-2.2.2 > Felix SCR ComponentRegistry leaves Timer thread running on deactivation. > -

[jira] [Commented] (FELIX-6501) ConcurrentModificationException during multiple reference field injection

[ https://issues.apache.org/jira/browse/FELIX-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485305#comment-17485305 ] Tom Watson commented on FELIX-6501: --- It seems we should use something like ConcurrentSk

[jira] [Commented] (FELIX-6479) Resolver should be able to bypass dynamic import package (by context configuration)

[ https://issues.apache.org/jira/browse/FELIX-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451188#comment-17451188 ] Tom Watson commented on FELIX-6479: --- More explanation is needed. Why would the resolve

[jira] [Commented] (FELIX-6463) Changing log levels for DS component getState and registration

[ https://issues.apache.org/jira/browse/FELIX-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424967#comment-17424967 ] Tom Watson commented on FELIX-6463: --- I'm in favor of reducing the noise of DEBUG becaus

[jira] [Commented] (FELIX-6429) IllegalArgumentException that should not happen

[ https://issues.apache.org/jira/browse/FELIX-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418326#comment-17418326 ] Tom Watson commented on FELIX-6429: --- I will point out the old OSGi bugzilla: https://g

[jira] [Commented] (FELIX-6458) Use ServiceReference.adaptTo(ServiceReferenceDTO)

[ https://issues.apache.org/jira/browse/FELIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416170#comment-17416170 ] Tom Watson commented on FELIX-6458: --- Yes, this seems like a good idea to me. > Use Ser

[jira] [Resolved] (FELIX-6439) Synchronization Issue while unbinding dynamic injected services

[ https://issues.apache.org/jira/browse/FELIX-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-6439. --- Fix Version/s: scr-2.1.30 Resolution: Fixed > Synchronization Issue while unbinding dynamic in

[jira] [Resolved] (FELIX-6408) SCR NPE in MultipleStaticReluctantCustomizer.modifiedService

[ https://issues.apache.org/jira/browse/FELIX-6408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-6408. --- Fix Version/s: scr-2.1.28 Resolution: Fixed I merged a fix for this. > SCR NPE in MultipleSta

[jira] [Resolved] (FELIX-6407) SCR Log Extension still logs using the log level of the extended bundle

[ https://issues.apache.org/jira/browse/FELIX-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-6407. --- Fix Version/s: scr-2.1.28 Resolution: Fixed I merged the PR. > SCR Log Extension still logs u

[jira] [Commented] (FELIX-6407) SCR Log Extension still logs using the log level of the extended bundle

[ https://issues.apache.org/jira/browse/FELIX-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346931#comment-17346931 ] Tom Watson commented on FELIX-6407: --- OK, I think I've finally located my cause of confu

[jira] [Commented] (FELIX-6407) SCR Log Extension still logs using the log level of the extended bundle

[ https://issues.apache.org/jira/browse/FELIX-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346424#comment-17346424 ] Tom Watson commented on FELIX-6407: --- The original PR introduced an OSGi-SCR-incompatibl

[jira] [Commented] (FELIX-6407) SCR Log Extension still logs using the log level of the extended bundle

[ https://issues.apache.org/jira/browse/FELIX-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346177#comment-17346177 ] Tom Watson commented on FELIX-6407: --- My understanding of the original solution is that

[jira] [Created] (FELIX-6408) SCR NPE in MultipleStaticReluctantCustomizer.modifiedService

Tom Watson created FELIX-6408: - Summary: SCR NPE in MultipleStaticReluctantCustomizer.modifiedService Key: FELIX-6408 URL: https://issues.apache.org/jira/browse/FELIX-6408 Project: Felix Issue T

[jira] [Commented] (FELIX-6398) Update framework packages to osgi.core 8

[ https://issues.apache.org/jira/browse/FELIX-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315535#comment-17315535 ] Tom Watson commented on FELIX-6398: --- Yes, that is the documentation I pointed to.  I ju

[jira] [Commented] (FELIX-6398) Update framework packages to osgi.core 8

[ https://issues.apache.org/jira/browse/FELIX-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315510#comment-17315510 ] Tom Watson commented on FELIX-6398: --- Not arguing against fixing this, it needs fixed ..

[jira] [Commented] (FELIX-6396) Multi-release jar bundles?

[ https://issues.apache.org/jira/browse/FELIX-6396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17306371#comment-17306371 ] Tom Watson commented on FELIX-6396: --- As of OSGi R7 MR JARs are supported: [https://doc

[jira] [Closed] (FELIX-6361) IllegalArgumentException possible from LoggerFactory.getLogger(Bundle, String, Class)

[ https://issues.apache.org/jira/browse/FELIX-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6361. - > IllegalArgumentException possible from LoggerFactory.getLogger(Bundle, > String, Class) >

[jira] [Closed] (FELIX-6353) Constructor injection: activation with optional reference fails if service not available

[ https://issues.apache.org/jira/browse/FELIX-6353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6353. - > Constructor injection: activation with optional reference fails if service > not available > -

[jira] [Closed] (FELIX-6351) EventDispatcher: Error during dispatch. (java.lang.IllegalStateException: Service already unregistered.)

[ https://issues.apache.org/jira/browse/FELIX-6351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6351. - > EventDispatcher: Error during dispatch. (java.lang.IllegalStateException: > Service already unregistered.)

[jira] [Closed] (FELIX-6352) SCR should protect against unregistered IllegalStateException for its ConfigurationListener registrations

[ https://issues.apache.org/jira/browse/FELIX-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6352. - > SCR should protect against unregistered IllegalStateException for its > ConfigurationListener registration

[jira] [Closed] (FELIX-6349) Possible NullPointerException on modified event in DependencyManager

[ https://issues.apache.org/jira/browse/FELIX-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6349. - > Possible NullPointerException on modified event in DependencyManager >

[jira] [Closed] (FELIX-6315) Factory components are eagerly deactivated

[ https://issues.apache.org/jira/browse/FELIX-6315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6315. - > Factory components are eagerly deactivated > -- > >

[jira] [Closed] (FELIX-6325) OSGi log package is mandatory but imported as optional

[ https://issues.apache.org/jira/browse/FELIX-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6325. - > OSGi log package is mandatory but imported as optional > --

[jira] [Closed] (FELIX-6327) NoSuchElementException can occur with SingleDynamicCustomizer when services are removed

[ https://issues.apache.org/jira/browse/FELIX-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6327. - > NoSuchElementException can occur with SingleDynamicCustomizer when services > are removed > --

[jira] [Commented] (FELIX-6387) SAX XML parser does not work properly

[ https://issues.apache.org/jira/browse/FELIX-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285205#comment-17285205 ] Tom Watson commented on FELIX-6387: --- Without any steps to reproduce it is going to be v

[jira] [Commented] (FELIX-6387) SAX XML parser does not work properly

[ https://issues.apache.org/jira/browse/FELIX-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282998#comment-17282998 ] Tom Watson commented on FELIX-6387: --- Do you have a component XML to reproduce? > SAX X

[jira] [Updated] (FELIX-6352) SCR should protect against unregistered IllegalStateException for its ConfigurationListener registrations

[ https://issues.apache.org/jira/browse/FELIX-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6352: -- Fix Version/s: scr-2.1.26 > SCR should protect against unregistered IllegalStateException for its > Co

[jira] [Commented] (FELIX-6382) Bundles failing to resolve because of missing java.* dependencies.

[ https://issues.apache.org/jira/browse/FELIX-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17272873#comment-17272873 ] Tom Watson commented on FELIX-6382: --- I suggest this be closed as not a bug (for Felix).

[jira] [Commented] (FELIX-6382) Bundles failing to resolve because of missing java.* dependencies.

[ https://issues.apache.org/jira/browse/FELIX-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17272440#comment-17272440 ] Tom Watson commented on FELIX-6382: --- What version of the framework are you running. St

[jira] [Commented] (FELIX-6379) Resolver keeps orphant dependency branches

[ https://issues.apache.org/jira/browse/FELIX-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271619#comment-17271619 ] Tom Watson commented on FELIX-6379: --- If the bundle is not part of the resolution result

[jira] [Commented] (FELIX-6378) NPE in ResolverImpl.java

[ https://issues.apache.org/jira/browse/FELIX-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270198#comment-17270198 ] Tom Watson commented on FELIX-6378: --- Can you give details on the environment where this

[jira] [Commented] (FELIX-6282) Felix Connect R7 support

[ https://issues.apache.org/jira/browse/FELIX-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270178#comment-17270178 ] Tom Watson commented on FELIX-6282: --- Atomos supports both Class Path and embedded in a

[jira] [Commented] (FELIX-6282) Felix Connect R7 support

[ https://issues.apache.org/jira/browse/FELIX-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269447#comment-17269447 ] Tom Watson commented on FELIX-6282: --- We have not released Atomos yet. Now that both Fe

[jira] [Commented] (FELIX-6163) ServiceTracker should not use System.currentTimeMillis() to check timeouts

[ https://issues.apache.org/jira/browse/FELIX-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17250333#comment-17250333 ] Tom Watson commented on FELIX-6163: --- [~karlpauls] for ServiceTracker did you fix this t

[jira] [Commented] (FELIX-6359) NPE while getting service does not lead to failover to the next implementation in SCR

[ https://issues.apache.org/jira/browse/FELIX-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241871#comment-17241871 ] Tom Watson commented on FELIX-6359: --- At this point I am not in favor of changing this b

[jira] [Commented] (FELIX-6359) NPE while getting service does not lead to failover to the next implementation in SCR

[ https://issues.apache.org/jira/browse/FELIX-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240833#comment-17240833 ] Tom Watson commented on FELIX-6359: --- Initial testcase confirms for a mandatory unary 1.

[jira] [Updated] (FELIX-6155) Add caching of service component metadata

[ https://issues.apache.org/jira/browse/FELIX-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6155: -- Fix Version/s: scr-2.1.18 > Add caching of service component metadata > ---

[jira] [Closed] (FELIX-6155) Add caching of service component metadata

[ https://issues.apache.org/jira/browse/FELIX-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson closed FELIX-6155. - > Add caching of service component metadata > - > > K

[jira] [Resolved] (FELIX-6155) Add caching of service component metadata

[ https://issues.apache.org/jira/browse/FELIX-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-6155. --- Resolution: Fixed Resolved in scr-2.1.18 > Add caching of service component metadata > -

[jira] [Commented] (FELIX-6359) NPE while getting service does not lead to failover to the next implementation in SCR

[ https://issues.apache.org/jira/browse/FELIX-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236455#comment-17236455 ] Tom Watson commented on FELIX-6359: --- I'm not sure the spec mandates such a fallback beh

[jira] [Updated] (FELIX-6361) IllegalArgumentException possible from LoggerFactory.getLogger(Bundle, String, Class)

[ https://issues.apache.org/jira/browse/FELIX-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6361: -- Fix Version/s: scr-2.1.26 > IllegalArgumentException possible from LoggerFactory.getLogger(Bundle, > S

[jira] [Assigned] (FELIX-6361) IllegalArgumentException possible from LoggerFactory.getLogger(Bundle, String, Class)

[ https://issues.apache.org/jira/browse/FELIX-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson reassigned FELIX-6361: - Assignee: Tom Watson > IllegalArgumentException possible from LoggerFactory.getLogger(Bundle, >

[jira] [Resolved] (FELIX-6361) IllegalArgumentException possible from LoggerFactory.getLogger(Bundle, String, Class)

[ https://issues.apache.org/jira/browse/FELIX-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson resolved FELIX-6361. --- Resolution: Fixed > IllegalArgumentException possible from LoggerFactory.getLogger(Bundle, > String,

[jira] [Commented] (FELIX-6361) IllegalArgumentException possible from LoggerFactory.getLogger(Bundle, String, Class)

[ https://issues.apache.org/jira/browse/FELIX-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236431#comment-17236431 ] Tom Watson commented on FELIX-6361: --- Fixed with https://github.com/apache/felix-dev/co

[jira] [Created] (FELIX-6361) IllegalArgumentException possible from LoggerFactory.getLogger(Bundle, String, Class)

Tom Watson created FELIX-6361: - Summary: IllegalArgumentException possible from LoggerFactory.getLogger(Bundle, String, Class) Key: FELIX-6361 URL: https://issues.apache.org/jira/browse/FELIX-6361 Project

[jira] [Updated] (FELIX-6314) NullPointerException in SingleComponentManager.disposeImplementationObject

[ https://issues.apache.org/jira/browse/FELIX-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Watson updated FELIX-6314: -- Fix Version/s: scr-2.1.22 > NullPointerException in SingleComponentManager.disposeImplementationObject

  1   2   >