[VOTE RESULT] Release Apache Felix Web Console 4.2.6
The vote passed with four binding +1 and one non binding +1 vote. No other votes have been cast. Thanks everyone for voting Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Closed] (FELIX-3864) Synchronized injection
[
https://issues.apache.org/jira/browse/FELIX-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tuomas Kiviaho closed FELIX-3864.
-
Resolution: Not a Problem
> Synchronized injection
> --
>
> Key: FELIX-3864
> URL: https://issues.apache.org/jira/browse/FELIX-3864
> Project: Felix
> Issue Type: Improvement
> Components: Dependency Manager
>Affects Versions: dependencymanager-3.0.0
>Reporter: Tuomas Kiviaho
>
> I see myself repeating the following pattern quite often
> {code}
>@ServiceDependency( removed = "removed", required=true )
> synchronized void added(LogService logService )
> {
> this.logService = logService;
> }
> synchronized void removed(LogService logService )
> {
> this.logService = null;
> }
> {code}
> Would it be possible to get optional synchronization support directly from
> dependency manager. I noticed that there's a sort of synchronization already
> taking place at ComponentImpl
> {code}
> private void configureImplementation(Class clazz, Object instance, String
> instanceName) {
> ...
> synchronized (SYNC) {
> field.set(serviceInstance,
> instance);
> }
> {code}
> I propose adding of 'boolean synchronization default false' attribute to
> @*Dependency which might contain a notion that this applies only to field
> injection. If syncronization between component's field injections is not
> needed then SYNC could be replaced with serviceInstance whenever the
> attribute is set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-4545) Implement Servlet Context Helper
[ https://issues.apache.org/jira/browse/FELIX-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4545: Fix Version/s: http-next > Implement Servlet Context Helper > > > Key: FELIX-4545 > URL: https://issues.apache.org/jira/browse/FELIX-4545 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: David Bosschaert >Assignee: Carsten Ziegeler > Fix For: http-next > > Attachments: patch.1614743.txt > > > Implement the Servlet Context Helper as described in RFC 189. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FELIX-4735) Cannot create a new factory configuration from Web Admin Console
[ https://issues.apache.org/jira/browse/FELIX-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-4735. --- > Cannot create a new factory configuration from Web Admin Console > > > Key: FELIX-4735 > URL: https://issues.apache.org/jira/browse/FELIX-4735 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-4.2.4 >Reporter: Valentin Valchev >Assignee: Valentin Valchev >Priority: Blocker > Fix For: webconsole-4.2.6 > > > The + button on any factory configuration doesn't work. So basically you are > unable to create a new factory config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FELIX-4738) Deprecate WebConsoleUtil#keyVal
[ https://issues.apache.org/jira/browse/FELIX-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-4738. --- > Deprecate WebConsoleUtil#keyVal > --- > > Key: FELIX-4738 > URL: https://issues.apache.org/jira/browse/FELIX-4738 > Project: Felix > Issue Type: Task > Components: Web Console >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: webconsole-4.2.6 > > > Unfortunately the current web console api depends on the json.org library. > Over the long term we should remove this dependency. Therefore we should > start with deprecating the method and replace it's usage within the > webconsole. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FELIX-4203) ConfigAdmin plugin does not return json
[ https://issues.apache.org/jira/browse/FELIX-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-4203. --- > ConfigAdmin plugin does not return json > --- > > Key: FELIX-4203 > URL: https://issues.apache.org/jira/browse/FELIX-4203 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-4.2.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: webconsole-4.2.6 > > > Requesting json for a single configuration, does always return the emtpy []: > For example: > http://localhost:4502/system/console/configMgr/org.apache.felix.eventadmin.impl.EventAdmin.json > The call to: > final Map services = ca.getServices( pid, pidFilter, > locale, false ); > always returns null -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FELIX-4734) Web Console RESTful API should wait for asynchonous operations until they complete
[
https://issues.apache.org/jira/browse/FELIX-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed FELIX-4734.
---
> Web Console RESTful API should wait for asynchonous operations until they
> complete
> ---
>
> Key: FELIX-4734
> URL: https://issues.apache.org/jira/browse/FELIX-4734
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-4.2.4
>Reporter: Konrad Windszus
>Assignee: Carsten Ziegeler
> Fix For: webconsole-4.2.6
>
> Attachments: FELIX-4734.patch
>
>
> Currently the RESTful API
> (http://felix.apache.org/documentation/subprojects/apache-felix-web-console/web-console-restful-api.html)
> adds a delay of 800ms to the response to give the asynchronous operations
> enough time to complete successfully
> (https://github.com/apache/felix/blob/trunk/webconsole/src/main/java/org/apache/felix/webconsole/internal/core/BundlesServlet.java#L412).
> Instead the according listeners should be used which are notified upon
> completion of an asynchronous task.
> For {{refresh}} {{FrameworkWiring.refreshBundles}} can be used
> (http://www.osgi.org/javadoc/r4v43/core/org/osgi/framework/wiring/FrameworkWiring.html#refreshBundles%28java.util.Collection,%20org.osgi.framework.FrameworkListener...%29).
> A similar approach should be used for the other actions like uninstall,
> install, update, start, stop, ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (FELIX-4710) Web Console: Display templated name hint for factory configuration entries
[
https://issues.apache.org/jira/browse/FELIX-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed FELIX-4710.
---
> Web Console: Display templated name hint for factory configuration entries
> --
>
> Key: FELIX-4710
> URL: https://issues.apache.org/jira/browse/FELIX-4710
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: webconsole-4.2.2
>Reporter: Stefan Seifert
>Assignee: Carsten Ziegeler
> Fix For: webconsole-4.2.6
>
> Attachments: 141126_FELIX-4710_webconsole_namehint.patch,
> 150119_FELIX-4710_webconsole_namehint_update.patch,
> 150120_FELIX-4710_site_update.patch, factoryconfig.gif,
> factoryconfig_namehint.gif
>
>
> currently for each factory configuration entry in the web console only a very
> cryptic name is displayed, consisting of the factory PID and a GUID. this is
> very inconvenient esp. if there are a lot of entries and the user want to
> edit a specific one:
> !factoryconfig.gif!
> proposal: the author of the OSGi service with factory configuration should be
> able to provide a "nameHint" template to display a nice human-readable name,
> and display the pid+gui only as tooltip:
> !factoryconfig_namehint.gif!
> attached is a patch with draft implementation of this based on an optional
> service property {{webconsole.configurationFactory.nameHint}} which can be
> set on the service which can reference other property names with
> placeholders. the web console then displays this name hint with the
> configured values replaced.
> example (using SCR annotation):
> {code:java}
> @Property(name = "webconsole.configurationFactory.nameHint", value =
> "{serviceName}: {ribbonHosts}")
> {code}
> this will help on a lot of services, e.g. factory configurations for log
> configuration an others.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (FELIX-4746) Escape outputting filter parameter in service servlet
[ https://issues.apache.org/jira/browse/FELIX-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-4746. --- > Escape outputting filter parameter in service servlet > - > > Key: FELIX-4746 > URL: https://issues.apache.org/jira/browse/FELIX-4746 > Project: Felix > Issue Type: Improvement > Components: Web Console >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: webconsole-4.2.6 > > > The ServicesServlet outputs the value of the filter request parameter as is; > this needs escaping otherwise the html output might get destroyed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FELIX-4704) Show ranking in web console services plugin
[
https://issues.apache.org/jira/browse/FELIX-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed FELIX-4704.
---
> Show ranking in web console services plugin
> ---
>
> Key: FELIX-4704
> URL: https://issues.apache.org/jira/browse/FELIX-4704
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Reporter: Alexander Klimetschek
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: webconsole-4.2.6
>
> Attachments: FELIX-4704.patch, screenshot.png
>
>
> The service ranking is an important property of services and one often needs
> to look for all implementations of a given service and sort them by their
> ranking - to list them in the order they are used by some other component.
> Thus adding a new column to the services table that can be sorted like the
> other ones would be really helpful. Filtering down to one service interface
> is already possible since FELIX-4202 (e.g. {{(objectclass=*.MyService}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (FELIX-4007) enable multiline inputs in Web Console Configuration
[ https://issues.apache.org/jira/browse/FELIX-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-4007. --- > enable multiline inputs in Web Console Configuration > > > Key: FELIX-4007 > URL: https://issues.apache.org/jira/browse/FELIX-4007 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-4.2.2 >Reporter: Oliver Lietz >Assignee: Carsten Ziegeler > Fix For: webconsole-4.2.6 > > Attachments: FELIX-4007.patch > > > me: Is there a reason not to use a single row textarea (rows="1") by default? > Felix: No ;-) > Never treally thought of this. But this could be a way to the solution. > Something like: > * textarea always > * if value contains CR/LF: > * as many rows as CR/LF > * unless there are more than say 5 CR/LF > * add keyboard event ensuring rows > 1 when > user hits return > http://mail-archives.apache.org/mod_mbox/felix-users/201206.mbox/%3c6dbbc039-77fa-4bc7-a55a-193360c3e...@adobe.com%3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FELIX-3849) Support setting configuration binding
[ https://issues.apache.org/jira/browse/FELIX-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-3849. --- > Support setting configuration binding > - > > Key: FELIX-3849 > URL: https://issues.apache.org/jira/browse/FELIX-3849 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Felix Meschberger >Assignee: Carsten Ziegeler > Fix For: webconsole-4.2.6 > > > When a configuration is used it is generally bound to the bundle of the > configuration consumer. The intent originally was that configurations can > only be consumed by a single bundle (actually a single consumer such as a > ManagedService registered with the configuration's service.pid). > As of recent Configuration Admin specifications the configuration binding has > been defined more openly such that configurations can be shared amongst > consumers in different bundles. > The web console currently only displays the bound location and allows for > clearing the binding (setting it to null). To fully support the new > configuration location regions, GUI should be provided to change or set the > location to some explicit string, such as "?*" to not restrict the > configurations use at all. > Also, the web console should be extended to by default set a configuration > location. For backwards compatibility it would probably make sense to have > such functionality configurable, since Configuration Admin implementations > not supporting the location regions would fail using configurations bound to > locations such as "?*". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (FELIX-4737) Provide an option to use system bundle context to get bundles/services (Support for subsystems)
[ https://issues.apache.org/jira/browse/FELIX-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-4737. --- > Provide an option to use system bundle context to get bundles/services > (Support for subsystems) > --- > > Key: FELIX-4737 > URL: https://issues.apache.org/jira/browse/FELIX-4737 > Project: Felix > Issue Type: Improvement > Components: Web Console >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: webconsole-4.2.6 > > > When the webconsole is used in an installation using subsystems, depending on > the installed subsystem types, not all bundles or services are visible to the > web console including the region bundles from subsystems. > While this might be desired in some situations, it makes the web console > rather useless when subsystems are used as these are completely invisible to > the administrator. > The best option would be to have a subsystem aware web console, but I fear > this would be a long way to go. Therefore I think we should simply use the > system bundle to get all bundles/services. And make this configurable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Felix Http 2.4.0
> On 29 Jan 2015, at 13:51, Carsten Ziegeler wrote: > > We solved 3 issues in this release, the most important one is the update > to Jetty 9 > > https://issues.apache.org/jira/browse/FELIX/fixforversion/12327075 > > This release includes only the changed modules compared to the 2.3.2 > release. > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-1051/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 1051 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) +1, validated the signatures and all sources compile and test correctly. -- Met vriendelijke groeten | Kind regards Jan Willem Janssen | Software Architect +31 631 765 814 My world is revolving around INAETICS and Amdatu Luminis Technologies B.V. Churchillplein 1 7314 BZ Apeldoorn +31 88 586 46 00 http://www.luminis-technologies.com http://www.luminis.eu KvK (CoC) 09 16 28 93 BTW (VAT) NL8169.78.566.B.01 signature.asc Description: Message signed with OpenPGP using GPGMail
[jira] [Created] (FELIX-4777) Dynamic initialization time configuration of @ConfigurationDependency
Tuomas Kiviaho created FELIX-4777:
-
Summary: Dynamic initialization time configuration of
@ConfigurationDependency
Key: FELIX-4777
URL: https://issues.apache.org/jira/browse/FELIX-4777
Project: Felix
Issue Type: Improvement
Components: Dependency Manager
Environment: 3.2.0
Reporter: Tuomas Kiviaho
{{@ConfigurationDependency}} annotation is missing the {{name}} method whitch
would allow to postpone the callback methods after initialization.
I stumbled upon this problem when I needed JTA at {{updated}} method but the
manager (via service dependency) was not yet available.
As a bonus one could then add support for metadata customization and have an
impact on {{required}} based on information gathered from
dependencies/injections that have already arrived at this point (BTW: currently
it's just hardcoded as {{true}} although the metadata - already as it is -
would be useful even in {{false}} mode).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
