[jira] [Resolved] (FELIX-6727) NullPointerException when using REST API to install a bundle
[
https://issues.apache.org/jira/browse/FELIX-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-6727.
-
Resolution: Fixed
https://github.com/apache/felix-dev/commit/16d6f9bdeacaf8568f350613c13ccb64c7ef0490
> NullPointerException when using REST API to install a bundle
>
>
> Key: FELIX-6727
> URL: https://issues.apache.org/jira/browse/FELIX-6727
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-5.0.6
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: webconsole-5.0.8
>
>
> When a bundle is installed via the REST API below NullPointerException might
> occur. The reason is that the detection of whether a response has already
> been written is based on status, error or content type - but the
> BundlesServlet only sets content length
> {code:java}
> 12.09.2024 09:11:44.086 *ERROR* [qtp1970453787-65] org.apache.felix.http
> Exception while processing request to /system/console/install
> java.lang.NullPointerException: Cannot read field "bundleRequested" because
> "reqInfo" is null
> at
> org.apache.felix.webconsole.internal.core.BundlesServlet.renderContent(BundlesServlet.java:523)
> at
> org.apache.felix.webconsole.internal.servlet.EnhancedPluginAdapter.renderContent(EnhancedPluginAdapter.java:158)
> at
> org.apache.felix.webconsole.internal.servlet.AbstractPluginAdapter.doGet(AbstractPluginAdapter.java:124)
> at
> org.apache.felix.webconsole.internal.servlet.EnhancedPluginAdapter.service(EnhancedPluginAdapter.java:152)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FELIX-6727) NullPointerException when using REST API to install a bundle
Carsten Ziegeler created FELIX-6727:
---
Summary: NullPointerException when using REST API to install a
bundle
Key: FELIX-6727
URL: https://issues.apache.org/jira/browse/FELIX-6727
Project: Felix
Issue Type: Bug
Components: Web Console
Affects Versions: webconsole-5.0.6
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: webconsole-5.0.8
When a bundle is installed via the REST API below NullPointerException might
occur. The reason is that the detection of whether a response has already been
written is based on status, error or content type - but the BundlesServlet only
sets content length
{source}
12.09.2024 09:11:44.086 *ERROR* [qtp1970453787-65] org.apache.felix.http
Exception while processing request to /system/console/install
java.lang.NullPointerException: Cannot read field "bundleRequested" because
"reqInfo" is null
at
org.apache.felix.webconsole.internal.core.BundlesServlet.renderContent(BundlesServlet.java:523)
at
org.apache.felix.webconsole.internal.servlet.EnhancedPluginAdapter.renderContent(EnhancedPluginAdapter.java:158)
at
org.apache.felix.webconsole.internal.servlet.AbstractPluginAdapter.doGet(AbstractPluginAdapter.java:124)
at
org.apache.felix.webconsole.internal.servlet.EnhancedPluginAdapter.service(EnhancedPluginAdapter.java:152)
{source}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FELIX-6727) NullPointerException when using REST API to install a bundle
[
https://issues.apache.org/jira/browse/FELIX-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-6727:
Description:
When a bundle is installed via the REST API below NullPointerException might
occur. The reason is that the detection of whether a response has already been
written is based on status, error or content type - but the BundlesServlet only
sets content length
{code:java}
12.09.2024 09:11:44.086 *ERROR* [qtp1970453787-65] org.apache.felix.http
Exception while processing request to /system/console/install
java.lang.NullPointerException: Cannot read field "bundleRequested" because
"reqInfo" is null
at
org.apache.felix.webconsole.internal.core.BundlesServlet.renderContent(BundlesServlet.java:523)
at
org.apache.felix.webconsole.internal.servlet.EnhancedPluginAdapter.renderContent(EnhancedPluginAdapter.java:158)
at
org.apache.felix.webconsole.internal.servlet.AbstractPluginAdapter.doGet(AbstractPluginAdapter.java:124)
at
org.apache.felix.webconsole.internal.servlet.EnhancedPluginAdapter.service(EnhancedPluginAdapter.java:152)
{code}
was:
When a bundle is installed via the REST API below NullPointerException might
occur. The reason is that the detection of whether a response has already been
written is based on status, error or content type - but the BundlesServlet only
sets content length
{source}
12.09.2024 09:11:44.086 *ERROR* [qtp1970453787-65] org.apache.felix.http
Exception while processing request to /system/console/install
java.lang.NullPointerException: Cannot read field "bundleRequested" because
"reqInfo" is null
at
org.apache.felix.webconsole.internal.core.BundlesServlet.renderContent(BundlesServlet.java:523)
at
org.apache.felix.webconsole.internal.servlet.EnhancedPluginAdapter.renderContent(EnhancedPluginAdapter.java:158)
at
org.apache.felix.webconsole.internal.servlet.AbstractPluginAdapter.doGet(AbstractPluginAdapter.java:124)
at
org.apache.felix.webconsole.internal.servlet.EnhancedPluginAdapter.service(EnhancedPluginAdapter.java:152)
{source}
> NullPointerException when using REST API to install a bundle
>
>
> Key: FELIX-6727
> URL: https://issues.apache.org/jira/browse/FELIX-6727
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-5.0.6
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: webconsole-5.0.8
>
>
> When a bundle is installed via the REST API below NullPointerException might
> occur. The reason is that the detection of whether a response has already
> been written is based on status, error or content type - but the
> BundlesServlet only sets content length
> {code:java}
> 12.09.2024 09:11:44.086 *ERROR* [qtp1970453787-65] org.apache.felix.http
> Exception while processing request to /system/console/install
> java.lang.NullPointerException: Cannot read field "bundleRequested" because
> "reqInfo" is null
> at
> org.apache.felix.webconsole.internal.core.BundlesServlet.renderContent(BundlesServlet.java:523)
> at
> org.apache.felix.webconsole.internal.servlet.EnhancedPluginAdapter.renderContent(EnhancedPluginAdapter.java:158)
> at
> org.apache.felix.webconsole.internal.servlet.AbstractPluginAdapter.doGet(AbstractPluginAdapter.java:124)
> at
> org.apache.felix.webconsole.internal.servlet.EnhancedPluginAdapter.service(EnhancedPluginAdapter.java:152)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FELIX-6724) [scr] Cyclic Dependecy reported with activation policy = lazy
[
https://issues.apache.org/jira/browse/FELIX-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879274#comment-17879274
]
Christoph Läubrich commented on FELIX-6724:
---
To trigger this it is important that both bundles have the same start level, if
they have different start level (it does not mater who is started first then)
the error does not occur.
Also removing {code}immediate = true{code} makes the error go away.
> [scr] Cyclic Dependecy reported with activation policy = lazy
> -
>
> Key: FELIX-6724
> URL: https://issues.apache.org/jira/browse/FELIX-6724
> Project: Felix
> Issue Type: Bug
>Reporter: Christoph Läubrich
>Priority: Major
> Attachments: ds_cyclic_testcase.zip
>
>
> This was discovered as part of
> https://issues.apache.org/jira/browse/FELIX-6069 but actually is a bit
> different case (but maybe even causing this in other situations)
> Assume the following components:
> One implements a service in *Bundle B* and the interface is provided by
> *Bundle A* and it has *immediate="true"*
> {code}
> http://www.osgi.org/xmlns/scr/v1.4.0";
> deactivate="stop" immediate="true" init="1" name="ReceipeAssetHandler">
>
>
>
>
>
> {code}
> Then in Bundle A (that has activation policy = lazy and provides the service
> interface) we have a consumer with dynamic references:
> {code}
> http://www.osgi.org/xmlns/scr/v1.1.0";
> immediate="true" name="Manager">
>
>
>
> name="XHandler" policy="dynamic" unbind="removeListener"/>
> interface="AssetHandler" name="AssetHandler" policy="dynamic"
> unbind="removeAssetHandler"/>
>
>
> {code}
> now SCR complains about cyclic dependecy:
> {code}
> !ENTRY org.apache.felix.scr 4 0 2024-09-04 09:51:52.017
> !MESSAGE bundle org.apache.felix.scr:2.2.10 (107) Circular reference detected
> trying to get service {AssetHandler}={service.id=107, service.bundleid=22,
> service.scope=bundle,
> osgi.ds.satisfying.condition.target=(osgi.condition.id=true),
> component.name=ReceipeAssetHandler, component.id=36}
> stack of references:
> ServiceReference: {AssetHandler}={service.id=107, service.bundleid=22,
> service.scope=bundle,
> osgi.ds.satisfying.condition.target=(osgi.condition.id=true),
> component.name=ReceipeAssetHandler, component.id=36}
> ServiceReference: {Manager}={service.id=108, service.bundleid=169,
> service.scope=bundle,
> osgi.ds.satisfying.condition.target=(osgi.condition.id=true),
> component.name=Manager, component.id=37}
> {code}
> *Why this happens:*
> As activation of the implementation in *Bundle B* triggers also activation of
> the *Bundle A* (due to the classload) *in the same thread* the thread local
> of ComponentRegistry#circularInfos already contains *Reference B* (that is
> currently activating and has no chance yet to call leaveCreate) while now the
> consumer component is created and already "see" the not yet active component
> service and try to add it to the list (again) what triggers the error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FELIX-6724) [scr] Cyclic Dependecy reported with activation policy = lazy
[
https://issues.apache.org/jira/browse/FELIX-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879270#comment-17879270
]
Christoph Läubrich commented on FELIX-6724:
---
I added a testcase, if I run this inside Eclipse I get the following logoutput:
{code}Starting test.ds.manager.recipe
Starting test.ds.manager
!SESSION 2024-09-04 17:31:30.130 ---
eclipse.buildId=unknown
java.version=17.0.2
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=de_DE
Command-line arguments: -dev
file:/home/christoph/workspace/.metadata/.plugins/org.eclipse.pde.core/New_configuration/dev.properties
-os linux -ws gtk -arch x86_64 -consoleLog -console
!ENTRY org.apache.felix.scr 4 0 2024-09-04 17:31:30.582
!MESSAGE bundle org.apache.felix.scr:2.2.10 (10) Circular reference detected
trying to get service {test.ds.manager.AssetHandler}={service.id=34,
service.bundleid=1, service.scope=bundle,
osgi.ds.satisfying.condition.target=(osgi.condition.id=true),
component.name=test.ds.manager.recipe.ReceipeAssetHandler, component.id=0}
stack of references: ServiceReference:
{test.ds.manager.AssetHandler}={service.id=34, service.bundleid=1,
service.scope=bundle,
osgi.ds.satisfying.condition.target=(osgi.condition.id=true),
component.name=test.ds.manager.recipe.ReceipeAssetHandler, component.id=0}
!STACK 0
java.lang.Exception: stack trace
at
org.apache.felix.scr.impl.ComponentRegistry.enterCreate(ComponentRegistry.java:493)
at
org.apache.felix.scr.impl.BundleComponentActivator.enterCreate(BundleComponentActivator.java:722)
at
org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:901)
at
org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse$1.run(ServiceFactoryUse.java:226)
at
java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
at
org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryGetService(ServiceFactoryUse.java:223)
at
org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.getService(ServiceFactoryUse.java:118)
at
org.eclipse.osgi.internal.serviceregistry.ServiceConsumer$2.getService(ServiceConsumer.java:48)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:580)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.getService(ServiceRegistry.java:548)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.getService(BundleContextImpl.java:672)
at
org.apache.felix.scr.impl.manager.SingleRefPair.getServiceObject(SingleRefPair.java:88)
at
org.apache.felix.scr.impl.inject.methods.BindMethod.getServiceObject(BindMethod.java:675)
at
org.apache.felix.scr.impl.manager.DependencyManager.getServiceObject(DependencyManager.java:2625)
at
org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.prebind(DependencyManager.java:441)
at
org.apache.felix.scr.impl.manager.DependencyManager.prebind(DependencyManager.java:1843)
at
org.apache.felix.scr.impl.manager.AbstractComponentManager.collectDependencies(AbstractComponentManager.java:1060)
at
org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:955)
at
org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:785)
at
org.apache.felix.scr.impl.manager.AbstractComponentManager.enableInternal(AbstractComponentManager.java:674)
at
org.apache.felix.scr.impl.manager.AbstractComponentManager.enable(AbstractComponentManager.java:437)
at
org.apache.felix.scr.impl.manager.ConfigurableComponentHolder.enableComponents(ConfigurableComponentHolder.java:671)
at
org.apache.felix.scr.impl.BundleComponentActivator.initialEnable(BundleComponentActivator.java:310)
at
org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:613)
at org.apache.felix.scr.impl.Activator.access$200(Activator.java:75)
at
org.apache.felix.scr.impl.Activator$ScrExtension.start(Activator.java:480)
at
org.apache.felix.scr.impl.AbstractExtender.createExtension(AbstractExtender.java:196)
at
org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:169)
at
org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:49)
at
org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:490)
at
org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:1)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233)
at
org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java
[jira] [Commented] (FELIX-6069) SCR detects cyclic dependency for dynamically bound service
[
https://issues.apache.org/jira/browse/FELIX-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879206#comment-17879206
]
Christoph Läubrich commented on FELIX-6069:
---
I now created https://issues.apache.org/jira/browse/FELIX-6724 to specifically
track this (simpler) issue as it is obviously wrong reported here. I suspect
that this issue is also caused by a similar behavior but thats much harder to
analyze and address.
> SCR detects cyclic dependency for dynamically bound service
> ---
>
> Key: FELIX-6069
> URL: https://issues.apache.org/jira/browse/FELIX-6069
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.1.14
>Reporter: Andreas Lemmer
>Priority: Major
> Labels: cyclic, scr
>
> Problem case: A bundle with two components: Component1 binds Component2
> statically, Component2 binds Component1 dynamically. Both components have
> immediate=true (but changing that also doesn't help).
> When starting the bundle, there is (nearly always) a Framework error message
> from SCR:
> {{ERROR [org.apache.felix.scr] bundle org.apache.felix.scr:2.1.14
> (12)Circular reference detected trying to get service [Component1]}}
> {{stack of references: ServiceReference: [Component1]}}
> {{ServiceReference: [Component2]}}
> {{java.lang.Exception: stack trace}}
> {{at
> org.apache.felix.scr.impl.ComponentRegistry.enterCreate(ComponentRegistry.java:485)}}
> {{at
> org.apache.felix.scr.impl.BundleComponentActivator.enterCreate(BundleComponentActivator.java:735)}}
> {{at
> org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:882)}}
> SCR tries it again a few milliseconds later *which works*.
> The real problem here is the error logging indicating that something is not
> working. This is very disturbing, because the behavior changes from time to
> time which makes it very hard to see if something is really wrong or if it's
> just a temporary problem.
> In my opinion, SCR should first start Component2 without Component1, then
> start Component1 and then bind Component1 to Component2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FELIX-6724) [scr] Cyclic Dependecy reported with activation policy = lazy
Christoph Läubrich created FELIX-6724:
-
Summary: [scr] Cyclic Dependecy reported with activation policy =
lazy
Key: FELIX-6724
URL: https://issues.apache.org/jira/browse/FELIX-6724
Project: Felix
Issue Type: Bug
Reporter: Christoph Läubrich
This was discovered as part of https://issues.apache.org/jira/browse/FELIX-6069
but actually is a bit different case (but maybe even causing this in other
situations)
Assume the following components:
One implements a service in *Bundle B* and the interface is provided by *Bundle
A* and it has *immediate="true"*
{code}
http://www.osgi.org/xmlns/scr/v1.4.0";
deactivate="stop" immediate="true" init="1" name="ReceipeAssetHandler">
{code}
Then in Bundle A (that has activation policy = lazy and provides the service
interface) we have a consumer with dynamic references:
{code}
http://www.osgi.org/xmlns/scr/v1.1.0";
immediate="true" name="Manager">
{code}
now SCR complains about cyclic dependecy:
{code}
!ENTRY org.apache.felix.scr 4 0 2024-09-04 09:51:52.017
!MESSAGE bundle org.apache.felix.scr:2.2.10 (107) Circular reference detected
trying to get service {AssetHandler}={service.id=107, service.bundleid=22,
service.scope=bundle,
osgi.ds.satisfying.condition.target=(osgi.condition.id=true),
component.name=ReceipeAssetHandler, component.id=36}
stack of references:
ServiceReference: {AssetHandler}={service.id=107, service.bundleid=22,
service.scope=bundle,
osgi.ds.satisfying.condition.target=(osgi.condition.id=true),
component.name=ReceipeAssetHandler, component.id=36}
ServiceReference: {Manager}={service.id=108, service.bundleid=169,
service.scope=bundle,
osgi.ds.satisfying.condition.target=(osgi.condition.id=true),
component.name=Manager, component.id=37}
{code}
*Why this happens:*
As activation of the implementation in *Bundle B* triggers also activation of
the *Bundle A* (due to the classload) *in the same thread* the thread local of
ComponentRegistry#circularInfos already contains *Reference B* (that is
currently activating and has no chance yet to call leaveCreate) while now the
consumer component is created and already "see" the not yet active component
service and try to add it to the list (again) what triggers the error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FELIX-6069) SCR detects cyclic dependency for dynamically bound service
[
https://issues.apache.org/jira/browse/FELIX-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879152#comment-17879152
]
Andreas Lemmer commented on FELIX-6069:
---
I have found out that this problem is mainly caused by SCR using "bundle"
dependencies. If Component1 in Bundle1 implements Interface1 in Bundle2 and
Component2 in Bundle2 binds Interface1, this is already reported as circular
reference because Bundle1 requires Bundle2 (correct because of the interface
dependency) and in Felix SCR, Bundle2 "requires/wants" Bundle1 because it binds
a service from it.
The only way to make this work without problems is to move the interface to a
separate bundle.
Note that SCR often complains about circular references (often wrongly) and it
seems to work most of the time, we have found that sometimes (0.1%-1%), it
actually fails and doesn't start these components at all or doesn't bind the
references!
> SCR detects cyclic dependency for dynamically bound service
> ---
>
> Key: FELIX-6069
> URL: https://issues.apache.org/jira/browse/FELIX-6069
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.1.14
>Reporter: Andreas Lemmer
>Priority: Major
> Labels: cyclic, scr
>
> Problem case: A bundle with two components: Component1 binds Component2
> statically, Component2 binds Component1 dynamically. Both components have
> immediate=true (but changing that also doesn't help).
> When starting the bundle, there is (nearly always) a Framework error message
> from SCR:
> {{ERROR [org.apache.felix.scr] bundle org.apache.felix.scr:2.1.14
> (12)Circular reference detected trying to get service [Component1]}}
> {{stack of references: ServiceReference: [Component1]}}
> {{ServiceReference: [Component2]}}
> {{java.lang.Exception: stack trace}}
> {{at
> org.apache.felix.scr.impl.ComponentRegistry.enterCreate(ComponentRegistry.java:485)}}
> {{at
> org.apache.felix.scr.impl.BundleComponentActivator.enterCreate(BundleComponentActivator.java:735)}}
> {{at
> org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:882)}}
> SCR tries it again a few milliseconds later *which works*.
> The real problem here is the error logging indicating that something is not
> working. This is very disturbing, because the behavior changes from time to
> time which makes it very hard to see if something is really wrong or if it's
> just a temporary problem.
> In my opinion, SCR should first start Component2 without Component1, then
> start Component1 and then bind Component1 to Component2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FELIX-6069) SCR detects cyclic dependency for dynamically bound service
[
https://issues.apache.org/jira/browse/FELIX-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879132#comment-17879132
]
Christoph Läubrich commented on FELIX-6069:
---
I have an even more strange situation, I changed one component from being
immediate = false to immediate = true and got the mention error, but this
component has not any cyclic reference at all:
Component XML
{code}
http://www.osgi.org/xmlns/scr/v1.4.0";
deactivate="stop" immediate="true" init="1" name="ReceipeAssetHandler">
{code}
Consumer with dynamic references:
{code}
http://www.osgi.org/xmlns/scr/v1.1.0";
immediate="true" name="Manager">
{code}
now SCR complains
{code}
!ENTRY org.apache.felix.scr 4 0 2024-09-04 09:51:52.017
!MESSAGE bundle org.apache.felix.scr:2.2.10 (107) Circular reference detected
trying to get service {AssetHandler}={service.id=107, service.bundleid=22,
service.scope=bundle,
osgi.ds.satisfying.condition.target=(osgi.condition.id=true),
component.name=ReceipeAssetHandler, component.id=36}
stack of references:
ServiceReference: {AssetHandler}={service.id=107, service.bundleid=22,
service.scope=bundle,
osgi.ds.satisfying.condition.target=(osgi.condition.id=true),
component.name=ReceipeAssetHandler, component.id=36}
ServiceReference: {Manager}={service.id=108, service.bundleid=169,
service.scope=bundle,
osgi.ds.satisfying.condition.target=(osgi.condition.id=true),
component.name=Manager, component.id=37}
{code}
> You shouldn't use circular references, they are never going to be very
> reliable.
Actually they work and there are good reasons for them (e.g. listeners), and as
dynamic references can come and go anytime it is actually something the
component has to handle anyways. So any dynamic reference actually "breaks" the
cycle already.
Sadly I have not found yet a good way to reproduce the error standalone.
> SCR detects cyclic dependency for dynamically bound service
> ---
>
> Key: FELIX-6069
> URL: https://issues.apache.org/jira/browse/FELIX-6069
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.1.14
>Reporter: Andreas Lemmer
>Priority: Major
> Labels: cyclic, scr
>
> Problem case: A bundle with two components: Component1 binds Component2
> statically, Component2 binds Component1 dynamically. Both components have
> immediate=true (but changing that also doesn't help).
> When starting the bundle, there is (nearly always) a Framework error message
> from SCR:
> {{ERROR [org.apache.felix.scr] bundle org.apache.felix.scr:2.1.14
> (12)Circular reference detected trying to get service [Component1]}}
> {{stack of references: ServiceReference: [Component1]}}
> {{ServiceReference: [Component2]}}
> {{java.lang.Exception: stack trace}}
> {{at
> org.apache.felix.scr.impl.ComponentRegistry.enterCreate(ComponentRegistry.java:485)}}
> {{at
> org.apache.felix.scr.impl.BundleComponentActivator.enterCreate(BundleComponentActivator.java:735)}}
> {{at
> org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:882)}}
> SCR tries it again a few milliseconds later *which works*.
> The real problem here is the error logging indicating that something is not
> working. This is very disturbing, because the behavior changes from time to
> time which makes it very hard to see if something is really wrong or if it's
> just a temporary problem.
> In my opinion, SCR should first start Component2 without Component1, then
> start Component1 and then bind Component1 to Component2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FELIX-6723) Add missing filter wrappers
[ https://issues.apache.org/jira/browse/FELIX-6723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6723. - Resolution: Fixed Applied the PR and fixed build problems > Add missing filter wrappers > --- > > Key: FELIX-6723 > URL: https://issues.apache.org/jira/browse/FELIX-6723 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http.wrappers-1.1.6 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.wrappers-1.1.8 > > > The http wrappers currently do not cover the whole servlet API - but just > what is required for the http.base implementation. > Therefore some wrappers are missing > https://github.com/apache/felix-dev/pull/331 is a PR to add some of those -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FELIX-6723) Add missing filter wrappers
[ https://issues.apache.org/jira/browse/FELIX-6723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-6723: Description: The http wrappers currently do not cover the whole servlet API - but just what is required for the http.base implementation. Therefore some wrappers are missing https://github.com/apache/felix-dev/pull/331 is a PR to add some of those > Add missing filter wrappers > --- > > Key: FELIX-6723 > URL: https://issues.apache.org/jira/browse/FELIX-6723 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http.wrappers-1.1.6 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.wrappers-1.1.8 > > > The http wrappers currently do not cover the whole servlet API - but just > what is required for the http.base implementation. > Therefore some wrappers are missing > https://github.com/apache/felix-dev/pull/331 is a PR to add some of those -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6723) Add missing filter wrappers
Carsten Ziegeler created FELIX-6723: --- Summary: Add missing filter wrappers Key: FELIX-6723 URL: https://issues.apache.org/jira/browse/FELIX-6723 Project: Felix Issue Type: Improvement Components: HTTP Service Affects Versions: http.wrappers-1.1.6 Reporter: Carsten Ziegeler Fix For: http.wrappers-1.1.8 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-6722) Update to Jetty 12.0.12 / 11.0.23
[ https://issues.apache.org/jira/browse/FELIX-6722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6722. - Resolution: Fixed Thanks for the PR > Update to Jetty 12.0.12 / 11.0.23 > - > > Key: FELIX-6722 > URL: https://issues.apache.org/jira/browse/FELIX-6722 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.jetty-5.1.26, http.jetty12-1.0.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FELIX-6722) Update to Jetty 12.0.12 / 11.0.23
[ https://issues.apache.org/jira/browse/FELIX-6722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-6722: Fix Version/s: http.jetty-5.1.26 http.jetty12-1.0.16 > Update to Jetty 12.0.12 / 11.0.23 > - > > Key: FELIX-6722 > URL: https://issues.apache.org/jira/browse/FELIX-6722 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.jetty-5.1.26, http.jetty12-1.0.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FELIX-6722) Update to Jetty 12.0.12 / 11.0.23
[ https://issues.apache.org/jira/browse/FELIX-6722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rütter updated FELIX-6722: --- Summary: Update to Jetty 12.0.12 / 11.0.23 (was: Update to Jetty 12.0.12) > Update to Jetty 12.0.12 / 11.0.23 > - > > Key: FELIX-6722 > URL: https://issues.apache.org/jira/browse/FELIX-6722 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter >Assignee: Carsten Ziegeler >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FELIX-6722) Update to Jetty 12.0.12
[ https://issues.apache.org/jira/browse/FELIX-6722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rütter updated FELIX-6722: --- Fix Version/s: (was: http.jetty12-1.0.14) (was: http.jetty-5.1.24) > Update to Jetty 12.0.12 > --- > > Key: FELIX-6722 > URL: https://issues.apache.org/jira/browse/FELIX-6722 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter >Assignee: Carsten Ziegeler >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6722) Update to Jetty 12.0.12
Paul Rütter created FELIX-6722: -- Summary: Update to Jetty 12.0.12 Key: FELIX-6722 URL: https://issues.apache.org/jira/browse/FELIX-6722 Project: Felix Issue Type: Improvement Components: HTTP Service Reporter: Paul Rütter Assignee: Carsten Ziegeler Fix For: http.jetty12-1.0.14, http.jetty-5.1.24 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6721) CVE-2021-33813: Upgrade jdom to the latest version in maven-bundle-plugin
Xilai Dai created FELIX-6721: Summary: CVE-2021-33813: Upgrade jdom to the latest version in maven-bundle-plugin Key: FELIX-6721 URL: https://issues.apache.org/jira/browse/FELIX-6721 Project: Felix Issue Type: Improvement Components: Maven Bundle Plugin Affects Versions: maven-bundle-plugin-5.1.9 Reporter: Xilai Dai There is a HIGH CVE https://nvd.nist.gov/vuln/detail/CVE-2021-33813 detected in the maven-bundle-plugin. https://github.com/apache/felix-dev/blob/master/tools/maven-bundle-plugin/pom.xml#L274 org.jdom jdom 1.1 The latest jdom2/2.0.6.1 (https://search.maven.org/artifact/org.jdom/jdom2/2.0.6.1/jar) is the fix version for it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FELIX-6715) Incorrect link in "Using bundles" for /system/console/services/
[
https://issues.apache.org/jira/browse/FELIX-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed FELIX-6715.
---
> Incorrect link in "Using bundles" for /system/console/services/
> ---
>
> Key: FELIX-6715
> URL: https://issues.apache.org/jira/browse/FELIX-6715
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-5.0.4
>Reporter: Konrad Windszus
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: webconsole-5.0.6
>
>
> The link being rendered in the service details table for row "Using bundle"
> is incorrect as it contains a double slash between
> {{/system/console/bundles}} and the bundle id.
> The reason for that is that the link is composed in
> https://github.com/apache/felix-dev/blob/81edc6e48db29feae5d0deb0af23719f50ddcb2b/webconsole/src/main/resources/res/ui/services.js#L139
> from {{bundlePath}} + '/' + {{bundle.bundleId}}. However the {{bundlePath}}
> always ends with a trailing slash so you end up with double slashes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (FELIX-6718) Require Java 11
[ https://issues.apache.org/jira/browse/FELIX-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6718. --- > Require Java 11 > --- > > Key: FELIX-6718 > URL: https://issues.apache.org/jira/browse/FELIX-6718 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.webconsoleplugin-1.2.0 > > > As the Jetty implementation requires Java 11, we can require the same for the > web console plugin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FELIX-6719) Improve request info output
[ https://issues.apache.org/jira/browse/FELIX-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6719. --- > Improve request info output > --- > > Key: FELIX-6719 > URL: https://issues.apache.org/jira/browse/FELIX-6719 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.webconsoleplugin-1.2.0 > > > Right now, the request info output only lists the service ids of the servlet > and filters for a given path. > We could improve this, add information about the context, add bundle info (if > available) and make service and bundle ids clickable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FELIX-6717) Include status info about Preprocessors
[ https://issues.apache.org/jira/browse/FELIX-6717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6717. --- > Include status info about Preprocessors > --- > > Key: FELIX-6717 > URL: https://issues.apache.org/jira/browse/FELIX-6717 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.webconsoleplugin-1.2.0, http.inventoryprinter-1.0.2 > > > Information about preprocessors is currently missing -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FELIX-6716) Update to Jetty 11.0.22 / 12.0.11
[ https://issues.apache.org/jira/browse/FELIX-6716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6716. --- > Update to Jetty 11.0.22 / 12.0.11 > - > > Key: FELIX-6716 > URL: https://issues.apache.org/jira/browse/FELIX-6716 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter (BlueConic) >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.jetty12-1.0.14, http.jetty-5.1.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FELIX-6720) Enable virtual thread support in Jetty12
[ https://issues.apache.org/jira/browse/FELIX-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864583#comment-17864583 ] Carsten Ziegeler commented on FELIX-6720: - We should keep it as simple as possible, and reflection seems to be the simplest solution > Enable virtual thread support in Jetty12 > - > > Key: FELIX-6720 > URL: https://issues.apache.org/jira/browse/FELIX-6720 > Project: Felix > Issue Type: Improvement > Components: HTTP Service > Environment: Jdk 19+ >Reporter: Paul Rütter >Priority: Major > > I was reading > [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,] > and wondered if it would make sense to make this configurable in Felix HTTP > bundle for jetty12. > It would need adding here (conditionally), probably via using reflection to > support pre jdk 21. > [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279] > [~cziegeler] what do you think? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FELIX-6720) Enable virtual thread support in Jetty12
[ https://issues.apache.org/jira/browse/FELIX-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864579#comment-17864579 ] Carsten Ziegeler commented on FELIX-6720: - [~laeubi] True, tooling is too clever :) we now have a PR with reflection anyway. Its not nice, but ok for this case > Enable virtual thread support in Jetty12 > - > > Key: FELIX-6720 > URL: https://issues.apache.org/jira/browse/FELIX-6720 > Project: Felix > Issue Type: Improvement > Components: HTTP Service > Environment: Jdk 19+ >Reporter: Paul Rütter >Priority: Major > > I was reading > [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,] > and wondered if it would make sense to make this configurable in Felix HTTP > bundle for jetty12. > It would need adding here (conditionally), probably via using reflection to > support pre jdk 21. > [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279] > [~cziegeler] what do you think? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FELIX-6720) Enable virtual thread support in Jetty12
[ https://issues.apache.org/jira/browse/FELIX-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864576#comment-17864576 ] Christoph Läubrich commented on FELIX-6720: --- [~cziegeler] this wont work, as Java 21 + target 17 will still complain about API not present in Java 17. > Enable virtual thread support in Jetty12 > - > > Key: FELIX-6720 > URL: https://issues.apache.org/jira/browse/FELIX-6720 > Project: Felix > Issue Type: Improvement > Components: HTTP Service > Environment: Jdk 19+ >Reporter: Paul Rütter >Priority: Major > > I was reading > [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,] > and wondered if it would make sense to make this configurable in Felix HTTP > bundle for jetty12. > It would need adding here (conditionally), probably via using reflection to > support pre jdk 21. > [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279] > [~cziegeler] what do you think? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FELIX-6720) Enable virtual thread support in Jetty12
[ https://issues.apache.org/jira/browse/FELIX-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864545#comment-17864545 ] Carsten Ziegeler commented on FELIX-6720: - Well, we can compile using 21 with target 17; if then the call is behind an if statement, all should work. Of course if we want to use 17 for compiling, then we should revert to reflection > Enable virtual thread support in Jetty12 > - > > Key: FELIX-6720 > URL: https://issues.apache.org/jira/browse/FELIX-6720 > Project: Felix > Issue Type: Improvement > Components: HTTP Service > Environment: Jdk 19+ >Reporter: Paul Rütter >Priority: Major > > I was reading > [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,] > and wondered if it would make sense to make this configurable in Felix HTTP > bundle for jetty12. > It would need adding here (conditionally), probably via using reflection to > support pre jdk 21. > [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279] > [~cziegeler] what do you think? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FELIX-6720) Enable virtual thread support in Jetty12
[ https://issues.apache.org/jira/browse/FELIX-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864539#comment-17864539 ] Christoph Läubrich commented on FELIX-6720: --- Either use reflection or Multi-Release Jars... > Enable virtual thread support in Jetty12 > - > > Key: FELIX-6720 > URL: https://issues.apache.org/jira/browse/FELIX-6720 > Project: Felix > Issue Type: Improvement > Components: HTTP Service > Environment: Jdk 19+ >Reporter: Paul Rütter >Priority: Major > > I was reading > [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,] > and wondered if it would make sense to make this configurable in Felix HTTP > bundle for jetty12. > It would need adding here (conditionally), probably via using reflection to > support pre jdk 21. > [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279] > [~cziegeler] what do you think? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FELIX-6720) Enable virtual thread support in Jetty12
[
https://issues.apache.org/jira/browse/FELIX-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864532#comment-17864532
]
Carsten Ziegeler commented on FELIX-6720:
-
Sounds like a good addition, I guess we can just check the major java version
to be >= 21 (via System.getProperty("java.version") ) and then have a
configuration to enable this
> Enable virtual thread support in Jetty12
> -
>
> Key: FELIX-6720
> URL: https://issues.apache.org/jira/browse/FELIX-6720
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Environment: Jdk 19+
>Reporter: Paul Rütter
>Priority: Major
>
> I was reading
> [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,]
> and wondered if it would make sense to make this configurable in Felix HTTP
> bundle for jetty12.
> It would need adding here (conditionally), probably via using reflection to
> support pre jdk 21.
> [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279]
> [~cziegeler] what do you think?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FELIX-6720) Enable virtual thread support in Jetty12
[ https://issues.apache.org/jira/browse/FELIX-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rütter updated FELIX-6720: --- Description: I was reading [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,] and wondered if it would make sense to make this configurable in Felix HTTP bundle for jetty12. It would need adding here (conditionally), probably via using reflection to support pre jdk 21. [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279] [~cziegeler] what do you think? was: I was reading [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,] and wondered if it would make sense to make this configurable in Felix HTTP bundle for jetty12. It would need adding here (conditionally), probably vis using reflection to support pre jdk 21. [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279] [~cziegeler] what do you think? > Enable virtual thread support in Jetty12 > - > > Key: FELIX-6720 > URL: https://issues.apache.org/jira/browse/FELIX-6720 > Project: Felix > Issue Type: Improvement > Components: HTTP Service > Environment: Jdk 19+ >Reporter: Paul Rütter >Priority: Major > > I was reading > [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,] > and wondered if it would make sense to make this configurable in Felix HTTP > bundle for jetty12. > It would need adding here (conditionally), probably via using reflection to > support pre jdk 21. > [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279] > [~cziegeler] what do you think? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FELIX-6720) Enable virtual thread support in Jetty12
[ https://issues.apache.org/jira/browse/FELIX-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rütter updated FELIX-6720: --- Description: I was reading [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,] and wondered if it would make sense to make this configurable in Felix HTTP bundle for jetty12. It would need adding here (conditionally), probably vis using reflection to support pre jdk 21. [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279] [~cziegeler] what do you think? was: I was reading [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,] and wondered if it would make sense to make this configurable in Felix HTTP bundle for jetty12. It would need adding here (conditionally): [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279] [~cziegeler] what do you think? > Enable virtual thread support in Jetty12 > - > > Key: FELIX-6720 > URL: https://issues.apache.org/jira/browse/FELIX-6720 > Project: Felix > Issue Type: Improvement > Components: HTTP Service > Environment: Jdk 19+ >Reporter: Paul Rütter >Priority: Major > > I was reading > [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,] > and wondered if it would make sense to make this configurable in Felix HTTP > bundle for jetty12. > It would need adding here (conditionally), probably vis using reflection to > support pre jdk 21. > [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279] > [~cziegeler] what do you think? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FELIX-6720) Enable virtual thread support in Jetty12
[ https://issues.apache.org/jira/browse/FELIX-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rütter updated FELIX-6720: --- Component/s: HTTP Service > Enable virtual thread support in Jetty12 > - > > Key: FELIX-6720 > URL: https://issues.apache.org/jira/browse/FELIX-6720 > Project: Felix > Issue Type: Improvement > Components: HTTP Service > Environment: Jdk 19+ >Reporter: Paul Rütter >Priority: Major > > I was reading > [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,] > and wondered if it would make sense to make this configurable in Felix HTTP > bundle for jetty12. > It would need adding here (conditionally): > [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279] > [~cziegeler] what do you think? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6720) Enable virtual thread support in Jetty12
Paul Rütter created FELIX-6720: -- Summary: Enable virtual thread support in Jetty12 Key: FELIX-6720 URL: https://issues.apache.org/jira/browse/FELIX-6720 Project: Felix Issue Type: Improvement Environment: Jdk 19+ Reporter: Paul Rütter I was reading [https://jetty.org/docs/jetty/12/programming-guide/arch/threads.html#thread-pool-virtual-threads,] and wondered if it would make sense to make this configurable in Felix HTTP bundle for jetty12. It would need adding here (conditionally): [https://github.com/apache/felix-dev/blob/8b2d2faa3669472f50020f7165a076af103c76e9/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L279] [~cziegeler] what do you think? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-6473) Make BundlesStartedCheck simpler
[ https://issues.apache.org/jira/browse/FELIX-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6473. - Resolution: Won't Fix Closing due to inactivity > Make BundlesStartedCheck simpler > > > Key: FELIX-6473 > URL: https://issues.apache.org/jira/browse/FELIX-6473 > Project: Felix > Issue Type: Improvement > Components: Health Checks >Affects Versions: healthcheck.generalchecks 2.0.14 >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > > Redesign of BundlesStarted check to use streams and make it more readable. > The result of the check should be the same but some log messages change. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-6719) Improve request info output
[ https://issues.apache.org/jira/browse/FELIX-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6719. - Resolution: Fixed https://github.com/apache/felix-dev/commit/d7bc8f1bccf118a5fb55cf4b6a3d9710824a43cd > Improve request info output > --- > > Key: FELIX-6719 > URL: https://issues.apache.org/jira/browse/FELIX-6719 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.webconsoleplugin-1.1.2 > > > Right now, the request info output only lists the service ids of the servlet > and filters for a given path. > We could improve this, add information about the context, add bundle info (if > available) and make service and bundle ids clickable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6719) Improve request info output
Carsten Ziegeler created FELIX-6719: --- Summary: Improve request info output Key: FELIX-6719 URL: https://issues.apache.org/jira/browse/FELIX-6719 Project: Felix Issue Type: Improvement Components: HTTP Service Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: http.webconsoleplugin-1.1.2 Right now, the request info output only lists the service ids of the servlet and filters for a given path. We could improve this, add information about the context, add bundle info (if available) and make service and bundle ids clickable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6718) Require Java 11
Carsten Ziegeler created FELIX-6718: --- Summary: Require Java 11 Key: FELIX-6718 URL: https://issues.apache.org/jira/browse/FELIX-6718 Project: Felix Issue Type: Improvement Components: HTTP Service Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: http.webconsoleplugin-1.1.2 As the Jetty implementation requires Java 11, we can require the same for the web console plugin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-6718) Require Java 11
[ https://issues.apache.org/jira/browse/FELIX-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6718. - Resolution: Fixed https://github.com/apache/felix-dev/commit/f09555ceb8c4c178f838e5b60930099be0828dbf > Require Java 11 > --- > > Key: FELIX-6718 > URL: https://issues.apache.org/jira/browse/FELIX-6718 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.webconsoleplugin-1.1.2 > > > As the Jetty implementation requires Java 11, we can require the same for the > web console plugin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FELIX-6715) Incorrect link in "Using bundles" for /system/console/services/
[
https://issues.apache.org/jira/browse/FELIX-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned FELIX-6715:
---
Assignee: Carsten Ziegeler
> Incorrect link in "Using bundles" for /system/console/services/
> ---
>
> Key: FELIX-6715
> URL: https://issues.apache.org/jira/browse/FELIX-6715
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-5.0.4
>Reporter: Konrad Windszus
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: webconsole-5.0.6
>
>
> The link being rendered in the service details table for row "Using bundle"
> is incorrect as it contains a double slash between
> {{/system/console/bundles}} and the bundle id.
> The reason for that is that the link is composed in
> https://github.com/apache/felix-dev/blob/81edc6e48db29feae5d0deb0af23719f50ddcb2b/webconsole/src/main/resources/res/ui/services.js#L139
> from {{bundlePath}} + '/' + {{bundle.bundleId}}. However the {{bundlePath}}
> always ends with a trailing slash so you end up with double slashes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FELIX-6715) Incorrect link in "Using bundles" for /system/console/services/
[
https://issues.apache.org/jira/browse/FELIX-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-6715.
-
Resolution: Fixed
Thanks [~kwin] - PR applied
> Incorrect link in "Using bundles" for /system/console/services/
> ---
>
> Key: FELIX-6715
> URL: https://issues.apache.org/jira/browse/FELIX-6715
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-5.0.4
>Reporter: Konrad Windszus
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: webconsole-5.0.6
>
>
> The link being rendered in the service details table for row "Using bundle"
> is incorrect as it contains a double slash between
> {{/system/console/bundles}} and the bundle id.
> The reason for that is that the link is composed in
> https://github.com/apache/felix-dev/blob/81edc6e48db29feae5d0deb0af23719f50ddcb2b/webconsole/src/main/resources/res/ui/services.js#L139
> from {{bundlePath}} + '/' + {{bundle.bundleId}}. However the {{bundlePath}}
> always ends with a trailing slash so you end up with double slashes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FELIX-6715) Incorrect link in "Using bundles" for /system/console/services/
[
https://issues.apache.org/jira/browse/FELIX-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-6715:
Fix Version/s: webconsole-5.0.6
> Incorrect link in "Using bundles" for /system/console/services/
> ---
>
> Key: FELIX-6715
> URL: https://issues.apache.org/jira/browse/FELIX-6715
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-5.0.4
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: webconsole-5.0.6
>
>
> The link being rendered in the service details table for row "Using bundle"
> is incorrect as it contains a double slash between
> {{/system/console/bundles}} and the bundle id.
> The reason for that is that the link is composed in
> https://github.com/apache/felix-dev/blob/81edc6e48db29feae5d0deb0af23719f50ddcb2b/webconsole/src/main/resources/res/ui/services.js#L139
> from {{bundlePath}} + '/' + {{bundle.bundleId}}. However the {{bundlePath}}
> always ends with a trailing slash so you end up with double slashes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FELIX-6717) Include status info about Preprocessors
[ https://issues.apache.org/jira/browse/FELIX-6717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6717. - Resolution: Fixed Added preprocessors in https://github.com/apache/felix-dev/commit/f506e907d5ee3d68869ad01227b4f905d8495d0c > Include status info about Preprocessors > --- > > Key: FELIX-6717 > URL: https://issues.apache.org/jira/browse/FELIX-6717 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.webconsoleplugin-1.1.2, http.inventoryprinter-1.0.2 > > > Information about preprocessors is currently missing -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-6716) Update to Jetty 11.0.22 / 12.0.11
[ https://issues.apache.org/jira/browse/FELIX-6716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6716. - Resolution: Fixed Thanks [~paul_blueconic] > Update to Jetty 11.0.22 / 12.0.11 > - > > Key: FELIX-6716 > URL: https://issues.apache.org/jira/browse/FELIX-6716 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter (BlueConic) >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.jetty12-1.0.14, http.jetty-5.1.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FELIX-6716) Update to Jetty 11.0.22 / 12.0.11
[ https://issues.apache.org/jira/browse/FELIX-6716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-6716: Fix Version/s: http.jetty12-1.0.14 http.jetty-5.1.24 > Update to Jetty 11.0.22 / 12.0.11 > - > > Key: FELIX-6716 > URL: https://issues.apache.org/jira/browse/FELIX-6716 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter (BlueConic) >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.jetty12-1.0.14, http.jetty-5.1.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6717) Include status info about Preprocessors
Carsten Ziegeler created FELIX-6717: --- Summary: Include status info about Preprocessors Key: FELIX-6717 URL: https://issues.apache.org/jira/browse/FELIX-6717 Project: Felix Issue Type: Improvement Components: HTTP Service Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: http.webconsoleplugin-1.1.2, http.inventoryprinter-1.0.2 Information about preprocessors is currently missing -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FELIX-6714) Special request attributes might not be set with multiple wrappers
[ https://issues.apache.org/jira/browse/FELIX-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6714. --- > Special request attributes might not be set with multiple wrappers > -- > > Key: FELIX-6714 > URL: https://issues.apache.org/jira/browse/FELIX-6714 > Project: Felix > Issue Type: Bug > Components: HTTP Service >Affects Versions: http.wrappers-1.0.4, http.wrappers6-1.1.4, > http.jetty12-1.0.10, http.jetty-5.1.20 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.wrappers-1.1.6, http.wrappers-1.0.6, > http.jetty-5.1.22, http.jetty12-1.0.12 > > > When multiple layers of the http wrappers are used with custom wrappers in > between, special request attributes might not be set properly. This includes > attributes for error handling, include/forward request dispatching. > For example: > * the original request is a jakarta.servlet request > * this is wrapper in a javax.servlet request > * which is then wrapper by a javax.servlet request wrapper > * which is then wrapped by jakarta.servlet request wrapper > If now a special attribute is set on the latest request object, the > implementation of setAttribute causes it to be set first, but then calls > removeAttribute - which in turn will wipe out the value -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6715) Incorrect link in "Using bundles" for /system/console/services/
Konrad Windszus created FELIX-6715:
--
Summary: Incorrect link in "Using bundles" for
/system/console/services/
Key: FELIX-6715
URL: https://issues.apache.org/jira/browse/FELIX-6715
Project: Felix
Issue Type: Bug
Components: Web Console
Affects Versions: webconsole-5.0.4
Reporter: Konrad Windszus
The link being rendered in the service details table for row "Using bundle" is
incorrect as it contains a double slash between {{/system/console/bundles}} and
the bundle id.
The reason for that is that the link is composed in
https://github.com/apache/felix-dev/blob/81edc6e48db29feae5d0deb0af23719f50ddcb2b/webconsole/src/main/resources/res/ui/services.js#L139
from {{bundlePath}} + '/' + {{bundle.bundleId}}. However the {{bundlePath}}
always ends with a trailing slash so you end up with double slashes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (FELIX-6703) Missing conf properties in the documentation
[ https://issues.apache.org/jira/browse/FELIX-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6703. --- > Missing conf properties in the documentation > > > Key: FELIX-6703 > URL: https://issues.apache.org/jira/browse/FELIX-6703 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-5.0.2 >Reporter: Luca Palano >Assignee: Carsten Ziegeler >Priority: Major > Labels: webconsole > Fix For: webconsole-5.0.4 > > > The webconsole documentation doesn't report in the "[OSGi Configuration Admin > title|https://github.com/apache/felix-dev/tree/master/webconsole#osgi-configuration-admin]"; > section, the following configuration properties: > * shutdown.timeout > * reload.timeout > Introduced by FELIX-6356, already merged on master. > [Here|https://github.com/apache/felix-dev/pull/316] is my github PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FELIX-6712) Release Websonsole - without JSON License
[ https://issues.apache.org/jira/browse/FELIX-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6712. --- > Release Websonsole - without JSON License > -- > > Key: FELIX-6712 > URL: https://issues.apache.org/jira/browse/FELIX-6712 > Project: Felix > Issue Type: Wish > Components: Web Console >Affects Versions: webconsole-5.0.2 >Reporter: Stefan Bischof >Assignee: Carsten Ziegeler >Priority: Major > Fix For: webconsole-5.0.4 > > > the eclipse foundation IP checks always fail on webconsole because oif the > JSOn license. > [https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/15063] > this should be fixes with this commits: > h4. [cleanup Manifest and JSON - LICENSE > (|https://github.com/apache/felix-dev/commit/dd17a96ea9e21fbe000848f96aabcd347f938b11] > [#304|https://github.com/apache/felix-dev/pull/304] > [)|https://github.com/apache/felix-dev/commit/dd17a96ea9e21fbe000848f96aabcd347f938b11] > h4. [Remove mentioning of JSON > license|https://github.com/apache/felix-dev/commit/148fcbae4d2d68cc82290ebbdd38efcacd3e26ec] > Would be great to get a release 5.0.4 to pass the IP check > [~cziegeler] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-6714) Special request attributes might not be set with multiple wrappers
[ https://issues.apache.org/jira/browse/FELIX-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6714. - Resolution: Fixed Fixed in https://github.com/apache/felix-dev/commit/7a351beced09320ab306d117e9e54878754c93bf by reversing the order (first remove then set) Added test cases > Special request attributes might not be set with multiple wrappers > -- > > Key: FELIX-6714 > URL: https://issues.apache.org/jira/browse/FELIX-6714 > Project: Felix > Issue Type: Bug > Components: HTTP Service >Affects Versions: http.wrappers-1.0.4, http.wrappers6-1.1.4, > http.jetty12-1.0.10, http.jetty-5.1.20 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.wrappers6-1.1.6, http.wrappers-1.0.6, > http.jetty-5.1.22, http.jetty12-1.0.12 > > > When multiple layers of the http wrappers are used with custom wrappers in > between, special request attributes might not be set properly. This includes > attributes for error handling, include/forward request dispatching. > For example: > * the original request is a jakarta.servlet request > * this is wrapper in a javax.servlet request > * which is then wrapper by a javax.servlet request wrapper > * which is then wrapped by jakarta.servlet request wrapper > If now a special attribute is set on the latest request object, the > implementation of setAttribute causes it to be set first, but then calls > removeAttribute - which in turn will wipe out the value -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6714) Special request attributes might not be set with multiple wrappers
Carsten Ziegeler created FELIX-6714: --- Summary: Special request attributes might not be set with multiple wrappers Key: FELIX-6714 URL: https://issues.apache.org/jira/browse/FELIX-6714 Project: Felix Issue Type: Bug Components: HTTP Service Affects Versions: http.jetty-5.1.20, http.jetty12-1.0.10, http.wrappers6-1.1.4, http.wrappers-1.0.4 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: http.wrappers6-1.1.6, http.wrappers-1.0.6, http.jetty-5.1.22, http.jetty12-1.0.12 When multiple layers of the http wrappers are used with custom wrappers in between, special request attributes might not be set properly. This includes attributes for error handling, include/forward request dispatching. For example: * the original request is a jakarta.servlet request * this is wrapper in a javax.servlet request * which is then wrapper by a javax.servlet request wrapper * which is then wrapped by jakarta.servlet request wrapper If now a special attribute is set on the latest request object, the implementation of setAttribute causes it to be set first, but then calls removeAttribute - which in turn will wipe out the value -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6713) SCR ConfigurationChangeTest fails in CI-Action
Stefan Bischof created FELIX-6713: - Summary: SCR ConfigurationChangeTest fails in CI-Action Key: FELIX-6713 URL: https://issues.apache.org/jira/browse/FELIX-6713 Project: Felix Issue Type: Bug Components: Declarative Services (SCR) Affects Versions: scr-2.2.14 Environment: github ci Reporter: Stefan Bischof This Test is failing: TestClass: ConfigurationChangeTest Method: test_optional_multiple_dynamic_config_cardinality_threads Github CI-Action: [https://github.com/apache/felix-dev/actions/runs/9543335831/job/26299752788] Test-Result: 2024-06-17T07:26:01.3550091Z [INFO] Results: 2024-06-17T07:26:01.3550364Z [INFO] 2024-06-17T07:26:01.3550660Z [ERROR] Failures: 2024-06-17T07:26:01.3551684Z [ERROR] ConfigurationChangeTest.test_optional_multiple_dynamic_config_cardinality_threads:180->multipleTestCardinalityDynamicThreads:334 expected:<3> but was:<4> 2024-06-17T07:26:01.3552581Z [INFO] 2024-06-17T07:26:01.3553018Z [ERROR] Tests run: 198, Failures: 1, Errors: 0, Skipped: 0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3547) NPE in httplite on android creating Locale.
[
https://issues.apache.org/jira/browse/FELIX-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-3547.
-
Resolution: Won't Fix
> NPE in httplite on android creating Locale.
> ---
>
> Key: FELIX-3547
> URL: https://issues.apache.org/jira/browse/FELIX-3547
> Project: Felix
> Issue Type: Bug
> Components: Lightweight HTTP Service
> Environment: Android 2.3.x
>Reporter: Ed Schaller
>Assignee: Ken Gilmer
>Priority: Major
> Labels: patch
> Attachments: HttpServletRequestImpl.3547.patch
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> httplite/core/src/main/java/org/apache/felix/httplite/servlet/HttpServletRequestImpl.java
> contains the following at line 86:
> private final Locale m_locale = new Locale( System.getProperty(
> "user.language" ), System.getProperty( "user.country" ) );
> On Android (at least 2.3, other versions not tried) this produces a
> NullPointerException when HttpServletRequestImpl is constructed because the
> Locale constructor cannot handle null and neither property is defined by
> default on Android.
> This is trivial to work around with code like:
> if(System.getProperty("user.language")==null)
> System.setProperty("user.language",
> Locale.getDefault().getLanguage());
> if(System.getProperty("user.country")==null)
> System.setProperty("user.country", Locale.getDefault().getCountry());
> A easy solution is to replace the above line with:
> private final Locale m_locale = Locale.getDefault();
> This would cause each instance to have the same Local object. Although I
> would be surprised if this is an issue the following would also work:
> private final Locale m_locale = new Locale( System.getProperty(
> "user.language", Locale.getDefault().getLanguage() ), System.getProperty(
> "user.country" ) , Locale.getDefault().getCountry());
> I'm using httplite with the felx web console for debugging. Other than this
> bug and needing to set an uncaught exception handler so android doesn't force
> close the app all is working well (the memory usage plugin of coarse dose not
> work because it depends on jmx which android doesn't have.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FELIX-6712) Release Websonsole - without JSON License
[ https://issues.apache.org/jira/browse/FELIX-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6712. - Assignee: Carsten Ziegeler Resolution: Fixed > Release Websonsole - without JSON License > -- > > Key: FELIX-6712 > URL: https://issues.apache.org/jira/browse/FELIX-6712 > Project: Felix > Issue Type: Wish > Components: Web Console >Affects Versions: webconsole-5.0.2 >Reporter: Stefan Bischof >Assignee: Carsten Ziegeler >Priority: Major > Fix For: webconsole-5.0.4 > > > the eclipse foundation IP checks always fail on webconsole because oif the > JSOn license. > [https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/15063] > this should be fixes with this commits: > h4. [cleanup Manifest and JSON - LICENSE > (|https://github.com/apache/felix-dev/commit/dd17a96ea9e21fbe000848f96aabcd347f938b11] > [#304|https://github.com/apache/felix-dev/pull/304] > [)|https://github.com/apache/felix-dev/commit/dd17a96ea9e21fbe000848f96aabcd347f938b11] > h4. [Remove mentioning of JSON > license|https://github.com/apache/felix-dev/commit/148fcbae4d2d68cc82290ebbdd38efcacd3e26ec] > Would be great to get a release 5.0.4 to pass the IP check > [~cziegeler] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-6694) Update Felix HTTP readme
[ https://issues.apache.org/jira/browse/FELIX-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6694. - Resolution: Fixed > Update Felix HTTP readme > > > Key: FELIX-6694 > URL: https://issues.apache.org/jira/browse/FELIX-6694 > Project: Felix > Issue Type: New Feature > Components: HTTP Service >Reporter: Paul Rütter >Priority: Major > > The current documentation on > [https://github.com/apache/felix-dev/blob/master/http/README.md] seems pretty > outdated and could do with an update. > The things i run into: > * > [https://github.com/apache/felix-dev/blob/master/http/README.md#configuration-properties] > is not up to date with the code in > [https://github.com/apache/felix-dev/blob/master/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyConfig.java] > * Since there is a Jetty 11 and Jetty 12 based bundle, the documentation > should reflect this. Maybe move the relevant information to the README of the > bundles themselves? > * The documentation is not clear on which version one should pick, depending > on JavaEE vs JakartaEE. > * > [https://github.com/apache/felix-dev/blob/master/http/README.md#all-in-one-bundle-configuration-properties] > mentions properties no longer in the master branch > * Is the information on setting up HTTP/2 still up tp date? It seems > convoluted and outdated. > I could maybe put in a PR with some suggestions, but i would need help > clarying some aspects. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FELIX-6701) Jetty12 EE11 preparation
[ https://issues.apache.org/jira/browse/FELIX-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6701. --- > Jetty12 EE11 preparation > - > > Key: FELIX-6701 > URL: https://issues.apache.org/jira/browse/FELIX-6701 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter >Priority: Major > > Jakarta EE 11 should be released within a couple of months, thus Jetty will > follow with a 12.1.x ([https://webtide.com/introducing-jetty-12/). > |https://webtide.com/introducing-jetty-12/).]Ideally, this will become a new > feature of the Jetty12 bundle. > What are the ideas to support this? > For the light bundle, i can imagine that the EE11 classes can be detected in > the classloader, like is done for websocket support. For the main jar, would > both EE10 and EE11 servlet classes be part of it? Or would we introduce new > classifiers for EE11 servlet? Probably, a new configuration option is needed > to specify the EE version to run. > These imports would be problematic if the EE10 classes are not available, > [https://github.com/apache/felix-dev/blob/517f9a0c89cad1866f315255568b40c568f5239d/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L34.] > > Just wondering how new (or existing 8/9, for that matter) EE specifications > would be part of the jetty12 bundle. Of course, we could already try it out > with EE9 as an exercise to ease transition to Jetty12. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-6701) Jetty12 EE11 preparation
[ https://issues.apache.org/jira/browse/FELIX-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6701. - Resolution: Fixed > Jetty12 EE11 preparation > - > > Key: FELIX-6701 > URL: https://issues.apache.org/jira/browse/FELIX-6701 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter >Priority: Major > > Jakarta EE 11 should be released within a couple of months, thus Jetty will > follow with a 12.1.x ([https://webtide.com/introducing-jetty-12/). > |https://webtide.com/introducing-jetty-12/).]Ideally, this will become a new > feature of the Jetty12 bundle. > What are the ideas to support this? > For the light bundle, i can imagine that the EE11 classes can be detected in > the classloader, like is done for websocket support. For the main jar, would > both EE10 and EE11 servlet classes be part of it? Or would we introduce new > classifiers for EE11 servlet? Probably, a new configuration option is needed > to specify the EE version to run. > These imports would be problematic if the EE10 classes are not available, > [https://github.com/apache/felix-dev/blob/517f9a0c89cad1866f315255568b40c568f5239d/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L34.] > > Just wondering how new (or existing 8/9, for that matter) EE specifications > would be part of the jetty12 bundle. Of course, we could already try it out > with EE9 as an exercise to ease transition to Jetty12. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FELIX-6694) Update Felix HTTP readme
[ https://issues.apache.org/jira/browse/FELIX-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6694. --- > Update Felix HTTP readme > > > Key: FELIX-6694 > URL: https://issues.apache.org/jira/browse/FELIX-6694 > Project: Felix > Issue Type: New Feature > Components: HTTP Service >Reporter: Paul Rütter >Priority: Major > > The current documentation on > [https://github.com/apache/felix-dev/blob/master/http/README.md] seems pretty > outdated and could do with an update. > The things i run into: > * > [https://github.com/apache/felix-dev/blob/master/http/README.md#configuration-properties] > is not up to date with the code in > [https://github.com/apache/felix-dev/blob/master/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyConfig.java] > * Since there is a Jetty 11 and Jetty 12 based bundle, the documentation > should reflect this. Maybe move the relevant information to the README of the > bundles themselves? > * The documentation is not clear on which version one should pick, depending > on JavaEE vs JakartaEE. > * > [https://github.com/apache/felix-dev/blob/master/http/README.md#all-in-one-bundle-configuration-properties] > mentions properties no longer in the master branch > * Is the information on setting up HTTP/2 still up tp date? It seems > convoluted and outdated. > I could maybe put in a PR with some suggestions, but i would need help > clarying some aspects. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3685) PackageAdmin WebConsole Plugin - Add support for non exported packages
[ https://issues.apache.org/jira/browse/FELIX-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3685. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > PackageAdmin WebConsole Plugin - Add support for non exported packages > -- > > Key: FELIX-3685 > URL: https://issues.apache.org/jira/browse/FELIX-3685 > Project: Felix > Issue Type: Improvement > Components: Web Console >Reporter: Chetan Mehrotra >Priority: Minor > Attachments: FELIX-3685.patch > > > Current implementation of PackageAdmin WebConsole plugin provides information > about those packages only which are exported by any bundle. It would be > helpful if it can also display information about those packages which are not > exported by any bundle. It would help in finding out which bundle packages > any class. > This information can be find out by using the bundle.getEntry(entryName) > method where the entryName is package name as path like > 'org/apache/sling/engine/impl'. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3614) In latest webconsole no property descriptors are available
[ https://issues.apache.org/jira/browse/FELIX-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3614. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > In latest webconsole no property descriptors are available > -- > > Key: FELIX-3614 > URL: https://issues.apache.org/jira/browse/FELIX-3614 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Jonathan Anstey >Assignee: Felix Meschberger >Priority: Major > Attachments: webconsole_metatype.patch, webconsole_metatype_2.patch > > > I noticed that in the latest webconsole (version 4.0.0) all items in the > config tab don't have the custom property descriptor shown - just default > ones with this message: > "This form is automatically generated from existing properties because no > property descriptors are available for this configuration. This may be cause > by the absence of the OSGi Metatype Service or the absence of a MetaType > descriptor for this configuration." > This problem didn't occur in the previous release of 3.1.8. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3415) Disable update button if bundle location URL is invalid
[
https://issues.apache.org/jira/browse/FELIX-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-3415.
-
Resolution: Won't Fix
no activity for years, closing as wont fix. please reopen if you think otherwise
> Disable update button if bundle location URL is invalid
> ---
>
> Key: FELIX-3415
> URL: https://issues.apache.org/jira/browse/FELIX-3415
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: webconsole-3.1.8
>Reporter: Felix Meschberger
>Priority: Major
>
> When clicking the update button on any bundle, the bundle location (or the
> bundle's update location header) is taken as an URL to retrieve a bundle
> update. If the bundle's update location header is not set and the bundle
> location is not a valid URL, this of course fails.
> We should probably disable the update button if the bundle location URL fails
> to be created:
> try {
> new URL(bundleLocation);
> updatePossible = true;
> } catch (MalformedURLException mue) {
> updatePossible = false;
> }
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FELIX-2754) Display licence overview
[ https://issues.apache.org/jira/browse/FELIX-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-2754. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Display licence overview > > > Key: FELIX-2754 > URL: https://issues.apache.org/jira/browse/FELIX-2754 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-3.1.6 >Reporter: Carsten Ziegeler >Priority: Major > > I think it would be nice if one could get an overview about the licences in > the bundles, like > - 12 bundles use Apache Licence V2 > - 3 bundles use BSD Licence > - 2 bundles have to licence info > The tricky part is to correctly detect the used licence. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-4890) Implement a MetaType service inventory printer
[ https://issues.apache.org/jira/browse/FELIX-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4890. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Implement a MetaType service inventory printer > -- > > Key: FELIX-4890 > URL: https://issues.apache.org/jira/browse/FELIX-4890 > Project: Felix > Issue Type: Task > Components: Web Console >Reporter: Felix Meschberger >Assignee: Felix Meschberger >Priority: Major > Fix For: webconsole-metatype-plugin-1.0.0 > > > For completeness of information of the status output of a framework > supporting inventory printing, it would be good to have an InventoryPrinter > for MetaType service information. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-5767) Webconsole binds only to a single HTTP context
[
https://issues.apache.org/jira/browse/FELIX-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-5767.
-
Resolution: Won't Fix
no activity for years, closing as wont fix. please reopen if you think otherwise
> Webconsole binds only to a single HTTP context
> --
>
> Key: FELIX-5767
> URL: https://issues.apache.org/jira/browse/FELIX-5767
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-4.2.18, webconsole-4.3.4
>Reporter: Joerg Hoh
>Priority: Major
>
> I want my application to be reachable by 2 different ways:
> * localhost via http (for easy maintenance)
> * on network interfaces only via https
> Therefor I created 2 different HTTP contexts, configured them accordingly and
> everything worked fine. But the webconsole was reachable only via 1 context.
> The description for the property "http.service.filter" of the "Apache Felix
> OSGI Management console" component states:
> {code}
> By default (if this property is not set or set to an emptystring) the Web
> Console binds with any Http Service available.
> {code}
> This doesn't seem to be the case. Also checking the code make me think, that
> the webconsole is only bound to a single (random) http context by default.
> But I need the webconsole reachable via more than 1 http context.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FELIX-4142) WebConsole doesn't allow installation of multiple versions of a bundle
[ https://issues.apache.org/jira/browse/FELIX-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4142. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > WebConsole doesn't allow installation of multiple versions of a bundle > -- > > Key: FELIX-4142 > URL: https://issues.apache.org/jira/browse/FELIX-4142 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-4.2.0 >Reporter: Jonathan Pierce >Priority: Minor > Attachments: BundlesServlet.patch > > > Currently when using the install button on the BundleServlet, it compares the > bundle symbolic name to determine whether or not to install (name match NOT > found), or update (name match found). It seems like it would be better to do > a comparison of the name and version so that multiple versions of a bundle > could be installed. Or at least add an option to the install dialog to allow > for it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-2163) The view for a single bundle uses the same multi-column view than for the bundles list, which is inapropriate
[ https://issues.apache.org/jira/browse/FELIX-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-2163. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > The view for a single bundle uses the same multi-column view than for the > bundles list, which is inapropriate > - > > Key: FELIX-2163 > URL: https://issues.apache.org/jira/browse/FELIX-2163 > Project: Felix > Issue Type: Improvement > Components: Web Console >Reporter: Guillaume Nodet >Priority: Major > > There's no real point in presenting the data in a multicolumn view, where you > have only one line with one huge cell and several cells which are mostly > redundant. I think we should have a slightly different view for viewing a > single bundle. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-4511) Read in and Set configuration for bundles from a file
[
https://issues.apache.org/jira/browse/FELIX-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-4511.
-
Resolution: Won't Fix
no activity for years, closing as wont fix. please reopen if you think otherwise
> Read in and Set configuration for bundles from a file
> -
>
> Key: FELIX-4511
> URL: https://issues.apache.org/jira/browse/FELIX-4511
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: configadmin-1.8.2
> Environment: Should work on all systems that Felix can run on.
>Reporter: Matthew Sadowski
>Priority: Minor
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> Program the ability to set the values of the properties for bundles based on
> a file.
> Currently there exists the the ability to output the configuration of all the
> bundles loaded onto the Felix system to a webpage in the configuration status
> page. There also exists the ability to download a hard copy of the file that
> was output. This feature would give the ability to upload the downloaded
> configuration file onto another instance of Felix. This would help replicate
> system configuration and load balance instances of Felix without worrying
> about human error in configuration copying.
> The updates could be :
> Ability to download bundle configuraiton file in JSON format.
> {
> "bunldes" : [
> {
> "bundleName" : "bname",
> "propertyName1" : "propertyValue",
> "propertyName2" : "propertyValue"
> }
> ]
> }
> Ability to upload JSON formatted bundle configuration file to easily
> configuration 1 or more named bundles.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FELIX-3523) Properly serialize multiple bundle installations
[ https://issues.apache.org/jira/browse/FELIX-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3523. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Properly serialize multiple bundle installations > > > Key: FELIX-3523 > URL: https://issues.apache.org/jira/browse/FELIX-3523 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-3.1.8 >Reporter: Felix Meschberger >Priority: Major > > Consider an administrator wishing to install a number of interdependent > bundles through the Web Console. There are basically two options: > (1) Multiple requests with one bundle after the other. Problem is that > installation takes place asynchronously and there is no easy and direct > feedback on the installation. Thus sending successive requests must be timed. > Not nice. > (2) Send one single request with multiple bundlefile parameters. > Unfortunately, this does not work either, because each bundle is installed in > its own thread. Not nice. > I see two solutions: > (a) add an option requesting synchronous installation instead of background > installation. When using HTTP clients such as cURL such an option can easily > be used and leveraged because there is little chance of deadlocks (which lead > to the asynchronous installation in the first place) > (b) implement a proper queue for asynchronous installation such that the > installation of multiple bundles can be properly serialized. This would have > the added benefit of not creating a new thread for each installation. > Caveat for synchronization: If the Web Console itself is to be updated, > synchronous installation/update may fail. Such an implementation much take > precaution. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-4194) Add authorization support to web console
[ https://issues.apache.org/jira/browse/FELIX-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4194. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Add authorization support to web console > > > Key: FELIX-4194 > URL: https://issues.apache.org/jira/browse/FELIX-4194 > Project: Felix > Issue Type: New Feature > Components: Web Console >Reporter: Carsten Ziegeler >Assignee: Georg Henzler >Priority: Major > > We should add some sort of authorization support to the web console, to > further restrict the possibilities. The main idea is to support the reading > and the "writing" use cases, so some user should only get read > (informational) access, while others have the ability to change things. > Started a thread in the mailing list to discuss the details further -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3955) Adding log download and tail plugin to Web Console
[ https://issues.apache.org/jira/browse/FELIX-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3955. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Adding log download and tail plugin to Web Console > -- > > Key: FELIX-3955 > URL: https://issues.apache.org/jira/browse/FELIX-3955 > Project: Felix > Issue Type: Improvement > Components: Web Console >Reporter: Henry Saginor >Priority: Minor > Attachments: logaccess.tar.gz > > > I would like to contribute a Web Console plugin which lets one tail and > download log files via browser. > Attaching initial cut bundle. > Note that at the moment this depends on SCR for configuration. This needs to > be refactored to use this with deployments without SCR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3711) Make more REST Urls available in UI (component id/name and service pid is often not clickable)
[ https://issues.apache.org/jira/browse/FELIX-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3711. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Make more REST Urls available in UI (component id/name and service pid is > often not clickable) > -- > > Key: FELIX-3711 > URL: https://issues.apache.org/jira/browse/FELIX-3711 > Project: Felix > Issue Type: New Feature > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Georg Henzler >Priority: Major > Attachments: > org.apache.felix.webconsole.patch-for-FELIX-3711-v2.patch, > org.apache.felix.webconsole.patch-make-rest-url-default-for-bundles.patch > > > Many REST urls already work if created manually, but are not yet available as > links in the UI: > http://localhost:8080/system/console/bundles/org.apache.felix.webconsole > http://localhost:8080/system/console/bundles/org.apache.felix.webconsole:4.0.1.SNAPSHOT > http://localhost:8080/system/console/configMgr/org.apache.felix.webconsole.plugins.event.internal.PluginServlet > http://localhost:8080/system/console/components/com.test.scr.ClassB > It would be easy to put the appropriate link behind the property values in > bundles/configuration/services detail views. > I use the REST Urls a lot as they are really valuable in email/instant > messenger/JIRA/WIKI to bring people with one click to the desired location, > therefore it would be nice to not have to construct them manually. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3255) Web Console should not create request URLs with double slashes
[ https://issues.apache.org/jira/browse/FELIX-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3255. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Web Console should not create request URLs with double slashes > -- > > Key: FELIX-3255 > URL: https://issues.apache.org/jira/browse/FELIX-3255 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-3.1.8 >Reporter: Felix Meschberger >Priority: Major > > As reported in [1] the web console might generate requests with double > slashes. This is not very nice and may in fact lead to failed requests. > [1] http://markmail.org/message/27pmmfdrpigdrylo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3563) Package Admin plugin should use Wiring API if available
[ https://issues.apache.org/jira/browse/FELIX-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3563. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Package Admin plugin should use Wiring API if available > --- > > Key: FELIX-3563 > URL: https://issues.apache.org/jira/browse/FELIX-3563 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-packageadmin-plugin 1.0.0 >Reporter: Felix Meschberger >Priority: Major > > Currently the Package Admin plugin uses the PackageAdmin service API to > analyze provided and required packages. > I would suggest the plugin is extended to leverage the R 4.3 Wiring API if > available in the framework. This would allow for more fine-grained > information to be printed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3152) JMX as web console feature
[ https://issues.apache.org/jira/browse/FELIX-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3152. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > JMX as web console feature > -- > > Key: FELIX-3152 > URL: https://issues.apache.org/jira/browse/FELIX-3152 > Project: Felix > Issue Type: New Feature > Components: Web Console >Reporter: Christanto >Priority: Major > Labels: jmx, webconsole > Attachments: org.apache.felix.webconsole.plugins.jmx.zip, > org.apache.felix.webconsole.plugins.jmx.zip, > org.apache.felix.webconsole.plugins.jmx.zip > > > The attached file is a source code that implement JMX client as felix web > console. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3403) Provide russian translations for new messages for the Log Service panel
[ https://issues.apache.org/jira/browse/FELIX-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3403. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Provide russian translations for new messages for the Log Service panel > --- > > Key: FELIX-3403 > URL: https://issues.apache.org/jira/browse/FELIX-3403 > Project: Felix > Issue Type: Sub-task > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Felix Meschberger >Priority: Major > > FELIX-3316 adds three new messages to be translated to russian: >log.traces=Exception details: >log.traces.full=Full Trace >log.traces.min=Message Only -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-4720) Web Console and Gogo rely on Log history buffer in the Log Service
[ https://issues.apache.org/jira/browse/FELIX-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4720. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Web Console and Gogo rely on Log history buffer in the Log Service > -- > > Key: FELIX-4720 > URL: https://issues.apache.org/jira/browse/FELIX-4720 > Project: Felix > Issue Type: Bug > Components: Gogo Command, Web Console >Reporter: Peter Kriens >Priority: Major > > The OSGi Log Reader Service has a command to get the history of the log. > However, the specification states that this history can be empty. The Equinox > framework is nowadays registering a Log Reader Service that has such an empty > history to prevent pinning objects in memory. > Using the history this way was always at odds with the specification since > the history was only intended to hold the start up events. The primary model > of the Log Service is a dispatcher. > I suggest that the Gogo log command and the Web Console maintain their own > history buffer to become independent on this fragile history buffer in the > Log Reader service. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3628) No Russian language suppor for Used Services Bundle Info Provider
[ https://issues.apache.org/jira/browse/FELIX-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3628. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > No Russian language suppor for Used Services Bundle Info Provider > - > > Key: FELIX-3628 > URL: https://issues.apache.org/jira/browse/FELIX-3628 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-4.2.0 >Reporter: Valentin Valchev >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3800) Support Category Translation
[ https://issues.apache.org/jira/browse/FELIX-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3800. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Support Category Translation > > > Key: FELIX-3800 > URL: https://issues.apache.org/jira/browse/FELIX-3800 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-4.2.4 > Environment: Defering open issues to the future release >Reporter: Felix Meschberger >Priority: Major > > FELIX-3769 added support to categorize the plugins to clean up the top > navigation and create menus. > The Category titles are not currently translated. It should be possible to > provide translations for those labels. Such translations should probably be > provided through the Web Console bundle. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3872) Russian Translations for making the default category configurable
[ https://issues.apache.org/jira/browse/FELIX-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3872. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Russian Translations for making the default category configurable > - > > Key: FELIX-3872 > URL: https://issues.apache.org/jira/browse/FELIX-3872 > Project: Felix > Issue Type: Task > Components: Web Console >Reporter: Felix Meschberger >Priority: Major > Fix For: webconsole-l10n-ru-1.0.0 > > > Please provide russian translations for the following labels: > metadata.category.name=Default Category > metadata.category.description=The default category (menu label) to be used \ > for plugins not registered with a felix.webconsole.category service \ > property or overwriting the AbstractWebConsole.getCategory() method. The \ > default value is "Main". > Thanks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-958) Add simple system update button based on Bundle Repository
[ https://issues.apache.org/jira/browse/FELIX-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-958. Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Add simple system update button based on Bundle Repository > -- > > Key: FELIX-958 > URL: https://issues.apache.org/jira/browse/FELIX-958 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-1.2.2 >Reporter: Felix Meschberger >Priority: Major > > A simple button should be added to the Bundle Repository page, which allows > with a single click to select and install the most recent versions of bundles > currently installed in the framework and thus allowing to update the system > to the latest state available from the bundle repository. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3880) [PATCH] placeholders for help links in the webconsole
[ https://issues.apache.org/jira/browse/FELIX-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3880. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > [PATCH] placeholders for help links in the webconsole > - > > Key: FELIX-3880 > URL: https://issues.apache.org/jira/browse/FELIX-3880 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Bertrand Delacretaz >Priority: Minor > Attachments: FELIX-3880.patch, helplinks.jpg > > > The attached patch adds placeholders for help links to the webconsole, like >class="configHelpLink" > data-config-param="ds.loglevel" > data-config-pid="org.apache.felix.scr.ScrService" > data-config-name="SCR Log Level" > data-config-description="Allows limiting the amount..." > > > which can be enhanced with client-side javascript to build customized help > links. > The patch also adds a script reference at the end of the config page: >type="text/javascript" > src="/system/console/overridable/scripts/confighelp.js"> > which by default points to an empty script provided by the FELIX-3879 > mechanism, overridable by providing a Servlet service that returns the > desired code. > I have created an example such servlet/script at > https://github.com/bdelacretaz/felix-confighelp-demo, to test this feature: > -Apply the FELIX-3879 patch and this patch and install the patched webconsole > -Install the felix-confighelp-demo bundle > -The /system/console/overridable/scripts/confighelp.js path must then return > the felix-confighelp-demo's confighelp.js script > -Open a config form in the console, help links should be present next to each > parameter, which point to google.com for the demo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3764) The servicediagnostics plugin does not append the correct context path info to it's javascript files
[ https://issues.apache.org/jira/browse/FELIX-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3764. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > The servicediagnostics plugin does not append the correct context path info > to it's javascript files > > > Key: FELIX-3764 > URL: https://issues.apache.org/jira/browse/FELIX-3764 > Project: Felix > Issue Type: Bug > Components: Web Console > Environment: org.apache.felix.servicediagnostics.plugin-0.1.1.jar >Reporter: Raymond Augé >Priority: Minor > Attachments: servicegraph.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-2185) easy plugin prototyping - tools for developers
[ https://issues.apache.org/jira/browse/FELIX-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-2185. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > easy plugin prototyping - tools for developers > -- > > Key: FELIX-2185 > URL: https://issues.apache.org/jira/browse/FELIX-2185 > Project: Felix > Issue Type: New Feature > Components: Web Console >Reporter: Valentin Valchev >Priority: Minor > Attachments: build.xml, build.xml > > > With the current web console, after being updated to JQuery + JQuery UI the > plugin structure becomes quite clear and simple: > 1. There is a Servlet (AbstractWebConsolePlugin), which main role is to > generate the required data for the plugin, typically a JSON and execute > actions. > 2. Although the actual rendering is in the Servlet, it use a template file, > that contains the HTML markup > 3. The main logic, that makes the interface interactive is JavaScript code, > that uses the JSON from the Servlet and modifies the HTML markup. > This separation makes it quite easy to develop applications in a static way > replacing the upper components with: > 1. a sample JSON data, statically generated > 2. a HTML file that is equals to : header + template + footer > 3. almost the same JavaScript code, that instead of using AJAX request to > obtain the data, uses the sample data in 1. > I must say, that personally have developer several plugins exactly using > static HTML file. > Although easy it consumes time to create that empty HTML file and start > developing the plugin. It would be much easier, if we have an option to > automatically generate a zip file - containing the HTML updated with the > latest header footer, the JavaScript libraries, included by default (e.g. > res/lib/) folder, common images and webconsole.css file. > This task can be easily achieved with modern build tools. Because my minimal > knowledge of the Maven build system, I've implemented that task in a simple > ANT build file, which must be placed in the webconsole root folder. When ant > is invoked with that file, it will generate a file named 'static-test.zip' > that contains a template, which is ready for modification and includes > up-to-date sources. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3879) [PATCH] overridable client scripts for the webconsole
[ https://issues.apache.org/jira/browse/FELIX-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3879. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > [PATCH] overridable client scripts for the webconsole > - > > Key: FELIX-3879 > URL: https://issues.apache.org/jira/browse/FELIX-3879 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Bertrand Delacretaz >Priority: Minor > Attachments: FELIX-3879.patch > > > This patch adds an OverridableResourcesServlet to the webconsole, that > handles the /overridable path and returns an empty response for paths like > /system/console/overridable/scripts/* > If a Servlet service with a org.apache.felix.resources.servlet=true service > property is present, it is used to handle those requests instead. > This can be used to provide extension points in the webconsole where users > can replace default do-nothing scripts with their own variants. > I'ill provide another patch that uses this feature for progressive > enhancement of the console config page with help links. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-2410) Provide simple template service factory console plugin
[ https://issues.apache.org/jira/browse/FELIX-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-2410. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Provide simple template service factory console plugin > -- > > Key: FELIX-2410 > URL: https://issues.apache.org/jira/browse/FELIX-2410 > Project: Felix > Issue Type: New Feature > Components: Web Console >Affects Versions: webconsole-3.0.0 >Reporter: Felix Meschberger >Priority: Major > Attachments: SimpleWebConsoleFactory.java > > > As a follow-up to FELIX-2246 a simple service factory to implement web > console plugins may be provided. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-931) Add bulk operations to web console
[ https://issues.apache.org/jira/browse/FELIX-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-931. Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Add bulk operations to web console > -- > > Key: FELIX-931 > URL: https://issues.apache.org/jira/browse/FELIX-931 > Project: Felix > Issue Type: Improvement > Components: Web Console >Reporter: Filippo Diotalevi >Priority: Minor > > It would be useful to have bulk operations in the web console: > - add a checkbox in each row (at the beginning) > - the user can select as many checkbox he wants > - the user can perform a bulk operation on the selected bundles (uninstall, > start, stop) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3878) Use metatype name and description in bundles and services consoles
[ https://issues.apache.org/jira/browse/FELIX-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3878. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Use metatype name and description in bundles and services consoles > -- > > Key: FELIX-3878 > URL: https://issues.apache.org/jira/browse/FELIX-3878 > Project: Felix > Issue Type: Improvement > Components: Web Console >Reporter: Jeff Young >Priority: Minor > > The configMgr console fetches out the name and description from the > OSGI-INF/metatype/metatype.properties file. It'd be nice if the bundles and > services consoles did as well. > You can currently get a description in the bundles and services consoles by > using the service.description property, but it's sub-optimal to have to > duplicate it between the metatype.properties file and the source file, and > the one in the source file is harder on translators. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3248) Display maven information for a bundle
[ https://issues.apache.org/jira/browse/FELIX-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3248. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Display maven information for a bundle > -- > > Key: FELIX-3248 > URL: https://issues.apache.org/jira/browse/FELIX-3248 > Project: Felix > Issue Type: New Feature > Components: Web Console >Affects Versions: webconsole-3.1.8 >Reporter: Carsten Ziegeler >Priority: Minor > > This depends on FELIX-2896. Once we are able to add bundle info provider, I > think it would be nice to have a provider reading the embedded pom and > displaying the maven coordinates etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-2886) The Webconsole shows private properties in plain text
[ https://issues.apache.org/jira/browse/FELIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-2886. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > The Webconsole shows private properties in plain text > - > > Key: FELIX-2886 > URL: https://issues.apache.org/jira/browse/FELIX-2886 > Project: Felix > Issue Type: Bug > Components: Web Console > Environment: An OSGi service property that starts with a '.' should > not be registered as a property nor should it be visible in the webconsole >Reporter: Peter Kriens >Priority: Major > > In oSGi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3765) CLONE - Commons IO dependency issue (webconsole packageadmin plugin)
[ https://issues.apache.org/jira/browse/FELIX-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3765. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > CLONE - Commons IO dependency issue (webconsole packageadmin plugin) > > > Key: FELIX-3765 > URL: https://issues.apache.org/jira/browse/FELIX-3765 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-packageadmin-plugin 1.0.0 >Reporter: Ivan Dubrov >Priority: Minor > Attachments: 3765-commons-io-webconsole-packageadmin.patch > > > Same as FELIX-3570, but for webconsole-packageadmin-plugin. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3120) Web console event plugin improvements
[ https://issues.apache.org/jira/browse/FELIX-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3120. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Web console event plugin improvements > - > > Key: FELIX-3120 > URL: https://issues.apache.org/jira/browse/FELIX-3120 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-event-plugin-1.0.2 >Reporter: Valentin Valchev >Priority: Major > > The event plugin must accept a list of topics for events to listen for > The event plugin must be able to be controlled to start/stop listen for > events. > The events queue size in the plugin must be configurable (default size could > be 100; for unlimited, as it is now -1 could be used). > It must be configurable which is the initial list of topics and whether the > plugin should start listen for events when it is started. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-4367) Memory Usage plugin creates dump when threshold is configured to 0
[ https://issues.apache.org/jira/browse/FELIX-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4367. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Memory Usage plugin creates dump when threshold is configured to 0 > -- > > Key: FELIX-4367 > URL: https://issues.apache.org/jira/browse/FELIX-4367 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-memoryusage-plugin-1.0.4 >Reporter: Rohit Kumar >Priority: Major > Attachments: FELIX-4367.patch > > > Memory usage plugin created memory dumps even when it was disabled by > configuring threshold percentage value to zero. This has been reproduced > when felix runs in embedded mode in any application server. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3634) User Admin Plugin - no Russian translation
[ https://issues.apache.org/jira/browse/FELIX-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3634. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > User Admin Plugin - no Russian translation > -- > > Key: FELIX-3634 > URL: https://issues.apache.org/jira/browse/FELIX-3634 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-useradmin-plugin-1.0.0 >Reporter: Valentin Valchev >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-2952) Error messages in memoryusage plugin swallowed
[
https://issues.apache.org/jira/browse/FELIX-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-2952.
-
Resolution: Won't Fix
no activity for years, closing as wont fix. please reopen if you think otherwise
> Error messages in memoryusage plugin swallowed
> --
>
> Key: FELIX-2952
> URL: https://issues.apache.org/jira/browse/FELIX-2952
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Reporter: Konrad Windszus
>Priority: Major
>
> Using Web Console 3.1.8 and Web Console Memory Usage Plugin 1.0.2 the result
> of the POST-Request after clicking "Dump Heap" is swallowed, because the page
> is automatically reloaded just after the pop-up dialog was shown. The
> timeframe is much too short to be able to read the message in the dialog.
> This is especially annoying in a case where the dialog says, something like:
> Failed dumping the heap, JVM does not provide known mechanism to create a
> Heap Dump. I can reproduce the behaviour with Chrome (11.0), Firefox (4.0.1).
> With IE7 I only get a Javascript error message when I load the Memory Usage
> plugin in the browser because of line 169:
> var __overall__ = {'Verbose Memory Output':'yes','Pending Finalizable
> Objects':'0','Overall Heap Memory Usage':'init = 1610612736(1572864K) used =
> 1705655200(1665678K) committed = 2147287040(2096960K) max =
> 2147287040(2096960K)','Overall Non-Heap Memory Usage':'init =
> 136773632(133568K) used = 421843952(411956K) committed = 671977472(656228K)
> max = 2197815296(2146304K)',};
> IE does not like that after the last comma (character 374 in that line)
> doesn't follow a string, label or number
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FELIX-3627) Web Console Shell plugin is not released
[ https://issues.apache.org/jira/browse/FELIX-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3627. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Web Console Shell plugin is not released > > > Key: FELIX-3627 > URL: https://issues.apache.org/jira/browse/FELIX-3627 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-shell-plugin-1.0.0 >Reporter: Valentin Valchev >Priority: Minor > > We've decided that we will separate web console and remove non-core osgi > services in different plugins. It seems that the shell plugin is not released > - there is no either download entry from Felix download page, nor artifact in > maven repository. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3629) No German language suppor for Used Services Bundle Info Provider
[ https://issues.apache.org/jira/browse/FELIX-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3629. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > No German language suppor for Used Services Bundle Info Provider > > > Key: FELIX-3629 > URL: https://issues.apache.org/jira/browse/FELIX-3629 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-4.2.0 >Reporter: Valentin Valchev >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-3773) WebConsole uses library with ASL-incompatible licence
[ https://issues.apache.org/jira/browse/FELIX-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3773. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > WebConsole uses library with ASL-incompatible licence > - > > Key: FELIX-3773 > URL: https://issues.apache.org/jira/browse/FELIX-3773 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Neil Bartlett >Priority: Critical > > WebConsole uses the JSON library from json.org that contains the following > term in its licence (http://www.json.org/license.html): > "The Software shall be used for Good, not Evil." > I believe that this restriction is incompatible with the ASL. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-2255) Display unresolved optional packages and dynamic imports when bundle is resolved
[ https://issues.apache.org/jira/browse/FELIX-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-2255. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > Display unresolved optional packages and dynamic imports when bundle is > resolved > > > Key: FELIX-2255 > URL: https://issues.apache.org/jira/browse/FELIX-2255 > Project: Felix > Issue Type: Wish > Components: Web Console >Affects Versions: webconsole-3.0.0 >Reporter: Carsten Ziegeler >Priority: Major > > If a bundle has an optional import which can't be resolved, this is not > visible in the bundle details anymore -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-5078) ServiceDiagnostics plugin wrong import package for dependencyManager
[ https://issues.apache.org/jira/browse/FELIX-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-5078. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > ServiceDiagnostics plugin wrong import package for dependencyManager > > > Key: FELIX-5078 > URL: https://issues.apache.org/jira/browse/FELIX-5078 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-servicediagnostics-plugin 0.1.3 > Environment: org.apache.felix.servicediagnostics.plugin-0.1.3.jar >Reporter: Arnaud MERGEY >Priority: Major > > Currently service diagnostics dependence with Dependency Manager is described > like this: > org.apache.felix.dm;version="[3.0,4)";resolution:=optional > first issue: it should not be optional as this plugin does not start without > it > second issue, max version is 4 (excluded) currently dependency manager is > 4.1.1 so this plugin cannot be used with it -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-5100) PackageAdmin WebConsole tab "Dependency Finder" always exposes the first maven dependency found in the bundle
[ https://issues.apache.org/jira/browse/FELIX-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-5100. - Resolution: Won't Fix no activity for years, closing as wont fix. please reopen if you think otherwise > PackageAdmin WebConsole tab "Dependency Finder" always exposes the first > maven dependency found in the bundle > - > > Key: FELIX-5100 > URL: https://issues.apache.org/jira/browse/FELIX-5100 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-packageadmin-plugin 1.0.2 >Reporter: Konrad Windszus >Priority: Minor > > To look up which maven dependency can be used for a certain package, the > Maven GAV information is extracted from the first "pom.properties" within > "META-INF/maven" of that bundle > (https://github.com/apache/felix-dev/blob/dba0764803da2b9228876fc1b2d4e8acc9115ed2/webconsole-plugins/packageadmin/src/main/java/org/apache/felix/webconsole/plugins/packageadmin/internal/WebConsolePlugin.java#L320) > That does > a) only work for bundles which have been created with the maven-bundle-plugin > b) only work in case the bundle does not embed other things > For example if you deploy > httpcore-osgi > (https://repo1.maven.org/maven2/org/apache/httpcomponents/httpcore-osgi/4.4.4/httpcore-osgi-4.4.4.pom) > which embeds two JARs the the "pom.properties" of one embedded jar > (httpcore-nio) is found first in the bundle whenever you look for any package > being exported by the bundle, e.g. "org.apache.http". > That algorithm should be more robust by additionally checking for the > packaging "bundle" in the according "pom.xml" in case there are multiple > "pom.properties" found! -- This message was sent by Atlassian Jira (v8.20.10#820010)
