[jira] [Updated] (FELIX-5277) WebConsole config admin styling is broken
[ https://issues.apache.org/jira/browse/FELIX-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev updated FELIX-5277: Summary: WebConsole config admin styling is broken (was: WebConsoel config admin styling is broken) > WebConsole config admin styling is broken > - > > Key: FELIX-5277 > URL: https://issues.apache.org/jira/browse/FELIX-5277 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-4.2.16 > Reporter: Valentin Valchev >Priority: Minor > Attachments: config-chrome.png, config-ff.png, config-ie.png > > > The web console config admin plugin styling is broken on properties with > cardinality > 1. > It seems, that this was a problem even before FELIX-5223. > The problem occurs, when you hit the plus button right to the property, to > add a next entry. I'm attaching few screenshot to illustrate the problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-5277) WebConsoel config admin styling is broken
Valentin Valchev created FELIX-5277: --- Summary: WebConsoel config admin styling is broken Key: FELIX-5277 URL: https://issues.apache.org/jira/browse/FELIX-5277 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-4.2.16 Reporter: Valentin Valchev Priority: Minor Attachments: config-chrome.png, config-ff.png, config-ie.png The web console config admin plugin styling is broken on properties with cardinality > 1. It seems, that this was a problem even before FELIX-5223. The problem occurs, when you hit the plus button right to the property, to add a next entry. I'm attaching few screenshot to illustrate the problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-5277) WebConsoel config admin styling is broken
[ https://issues.apache.org/jira/browse/FELIX-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev updated FELIX-5277: Attachment: config-ie.png config-ff.png config-chrome.png > WebConsoel config admin styling is broken > - > > Key: FELIX-5277 > URL: https://issues.apache.org/jira/browse/FELIX-5277 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-4.2.16 > Reporter: Valentin Valchev >Priority: Minor > Attachments: config-chrome.png, config-ff.png, config-ie.png > > > The web console config admin plugin styling is broken on properties with > cardinality > 1. > It seems, that this was a problem even before FELIX-5223. > The problem occurs, when you hit the plus button right to the property, to > add a next entry. I'm attaching few screenshot to illustrate the problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Felix WebConsole 4.2.16
+1 (non binding) On 31.5.2016 г. 10:44 ч., Carsten Ziegeler wrote: > We solved three issues in this release: > http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.webconsole-4.2.16/changelog.txt > > > Staging repositories: > https://repository.apache.org/content/repositories/orgapachefelix-1122/ > > 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 1122 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > Carsten -- Mit freundlichen Grüßen / Best regards *Valentin Valchev* ProSyst Software GmbH Senior Project Manager Aachener Str. 222 50931 Cologne Germany _www.prosyst.com_ <http://www.prosyst.com> <https://twitter.com/ProSystSoftware> <https://www.linkedin.com/company/prosyst> <https://www.facebook.com/ProSyst.OSGI?fref=ts> Tel. +359 (0)2 952 35 81 Fax +359 (0)2 953 26 17 _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. Dimitar Valtchev signature.asc Description: OpenPGP digital signature
[jira] [Comment Edited] (FELIX-5227) Created manifest files do not end with newline
[
https://issues.apache.org/jira/browse/FELIX-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215921#comment-15215921
]
Valentin Valchev edited comment on FELIX-5227 at 3/29/16 12:23 PM:
---
Hello Kai,
IMHO the problem is not only the bundle plugin. I've experienced similar
issues, when embedding signed jars inlined.
I've looked at your code:
https://github.com/eclipse/californium/blob/master/californium-osgi/pom.xml
The line that causes the problem is:
{code}
californium-core;inline=true,element-connector;inline=!about.html
{code}
When you inlined the dependency, probably it already has own signature files.
Those files are incomplete as they include one part of the embedded classes.
But in order to have a valid signed jar all entries must be signed.
In order to fix that problem you could:
* not inline the jar files (which is good, because you will also see the
embedded artifact versions)
* when inlining the files, also exclude all META-INF/*.SF,META-INF/*.RSA
If you do the above, you will be able to sign your bundle successfully.
was (Author: v_valchev):
Hello Kai,
IMHOthe problem is not the bundle plugin. I've experienced similar issues, when
embedding signed jars inlined.
I've looked at your code:
https://github.com/eclipse/californium/blob/master/californium-osgi/pom.xml
The line that causes the problem is:
{code}
californium-core;inline=true,element-connector;inline=!about.html
{code}
When you inlined the dependency, probably it already has own signature files.
Those files are incomplete as they include one part of the embedded classes.
But in order to have a valid signed jar all entries must be signed.
In order to fix that problem you could:
* not inline the jar files (which is good, because you will also see the
embedded artifact versions)
* when inlining the files, also exclude all META-INF/*.SF,META-INF/*.RSA
If you do the above, you will be able to sign your bundle successfully.
> Created manifest files do not end with newline
> --
>
> Key: FELIX-5227
> URL: https://issues.apache.org/jira/browse/FELIX-5227
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-3.0.1
> Environment: Linux
>Reporter: Kai Hudalla
> Attachments: californium-osgi-1.0.4-20160326.145623-2.jar
>
>
> Manifest files created by the maven bundle plugin do not end with a newline
> character. This is problematic when signing a bundle containing such a
> Manifest because the jarsigner tool then fails to insert an empty line
> between the last entry in the Manifest created by the bundle plugin (in my
> case the line containing the *tool:* header) and the first entry for signed
> files contained in the bundle.
> When later verifying such a signed bundle this results in jarsigner issuing a
> warning that the jar contains files for which no signature exists which I
> assume is because of the missing empty line.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FELIX-5227) Created manifest files do not end with newline
[
https://issues.apache.org/jira/browse/FELIX-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215921#comment-15215921
]
Valentin Valchev commented on FELIX-5227:
-
Hello Kai,
IMHOthe problem is not the bundle plugin. I've experienced similar issues, when
embedding signed jars inlined.
I've looked at your code:
https://github.com/eclipse/californium/blob/master/californium-osgi/pom.xml
The line that causes the problem is:
{code}
californium-core;inline=true,element-connector;inline=!about.html
{code}
When you inlined the dependency, probably it already has own signature files.
Those files are incomplete as they include one part of the embedded classes.
But in order to have a valid signed jar all entries must be signed.
In order to fix that problem you could:
* not inline the jar files (which is good, because you will also see the
embedded artifact versions)
* when inlining the files, also exclude all META-INF/*.SF,META-INF/*.RSA
If you do the above, you will be able to sign your bundle successfully.
> Created manifest files do not end with newline
> --
>
> Key: FELIX-5227
> URL: https://issues.apache.org/jira/browse/FELIX-5227
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
>Affects Versions: maven-bundle-plugin-3.0.1
> Environment: Linux
>Reporter: Kai Hudalla
> Attachments: californium-osgi-1.0.4-20160326.145623-2.jar
>
>
> Manifest files created by the maven bundle plugin do not end with a newline
> character. This is problematic when signing a bundle containing such a
> Manifest because the jarsigner tool then fails to insert an empty line
> between the last entry in the Manifest created by the bundle plugin (in my
> case the line containing the *tool:* header) and the first entry for signed
> files contained in the bundle.
> When later verifying such a signed bundle this results in jarsigner issuing a
> warning that the jar contains files for which no signature exists which I
> assume is because of the missing empty line.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FELIX-5168) source release of felix artifacts
Valentin Valchev created FELIX-5168: --- Summary: source release of felix artifacts Key: FELIX-5168 URL: https://issues.apache.org/jira/browse/FELIX-5168 Project: Felix Issue Type: Improvement Components: Main, Maven Bundle Plugin Reporter: Valentin Valchev Priority: Trivial Currently there is a "sources" artifact generated for every bundle, that is being released by the Felix community. Those sources however are not quite useful, if you do not develop a "maven" project. I'm using Eclipse - it is probably the main OSGi developers tool. The typical OSGi development model in Eclipse is to have a PDE project, which uses the so-called "Target Platforms". And target platform is usually a folder with bundles, and PDE resolves the dependencies manually. If the sources are generated with bnd, using the <_sources> tag, they are embedded in OSGI-OPT/src folder, inside the bundle. Those sources are automatically detected by Eclipse. However, if you generate a separate source bundle, Eclipse will be stupid enough not to consider that "XYZ-sources.jar" is the sources for "XYZ.jar". Instead it will expected that XYZ-sources.jar has a manifest entry "Eclipse-SourceBundle: XYZ". So, adding this header to the source releases will be great for all Eclipse PDE developers. -- Sorry, if I didn't set the correct component. I searched for Felix master POM, but didn't found any results. I've also added Maven Bundle Plugin component, because you guys probably also have an opinion on that matter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-5076) Website shows a lot of issues
[ https://issues.apache.org/jira/browse/FELIX-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954548#comment-14954548 ] Valentin Valchev commented on FELIX-5076: - There are multiple problems also with that page: http://felix.apache.org/documentation/subprojects/apache-felix-gogo/rfc-147-overview.html > Website shows a lot of issues > - > > Key: FELIX-5076 > URL: https://issues.apache.org/jira/browse/FELIX-5076 > Project: Felix > Issue Type: Improvement > Components: Documentation >Reporter: Rolf Geuenich > > On the projects website are a lot of glitches like doubled headings > (http://felix.apache.org/documentation/tutorials-examples-and-presentations/apache-felix-application-demonstration.html), > no line breaks > (http://felix.apache.org/documentation/development/building-felix.html), a > lot of markdown links which are shown in text form instead as a link > (http://felix.apache.org/documentation/tutorials-examples-and-presentations/apache-felix-application-demonstration.html), > dead links (http://felix.apache.org/documentation.html -> site map) etc. > I'm unable to find informations about how the webpage is generated or where > the files are stored. So I'm unable to help. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE RESULT] Release Felix Web Console version 4.2.12
done for all releases On 23/09/2015 16:55, Carsten Ziegeler wrote: > Am 23.09.15 um 14:37 schrieb Valentin Valchev: >> Hi, >> >> The vote has passed with three binding +1 votes and two non-binding: >> >> +1 (binding): Carsten Ziegeler, David Bosschaert, Pierre De Rop >> +1 (non binding): Jamie G, Jean-Baptiste Onofré >> >> I would ask a member of the Apache Felix PMC to promote the release and >> upload artifacts to maven central. >> (http://felix.apache.org/documentation/development/release-management-nexus.html#promoting-the-release) >> > Done, could you please also update the website (news + download) section? > > Thanks > Carsten -- Mit freundlichen Grüßen / Best regards *Valentin Valchev* ProSyst Software GmbH Senior Project Manager Aachener Str. 222 50931 Cologne Germany _www.prosyst.com_ <http://www.prosyst.com> <https://twitter.com/ProSystSoftware> <https://www.linkedin.com/company/prosyst> <https://www.facebook.com/ProSyst.OSGI?fref=ts> Tel. +359 (0)2 952 35 81 Fax +359 (0)2 953 26 17 _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. Dimitar Valtchev signature.asc Description: OpenPGP digital signature
[VOTE RESULT] Release Felix webconsole-packageadmin-plugin version 1.0.2
Hi, The vote has passed with three binding +1 votes and one non-binding: +1 (binding): Carsten Ziegeler, David Bosschaert, Pierre De Rop +1 (non binding): Jean-Baptiste Onofré I would ask a member of the Apache Felix PMC to promote the release and upload artifacts to maven central. (http://felix.apache.org/documentation/development/release-management-nexus.html#promoting-the-release) Meanwhile, I'll fix the versions in the JIRA project. Regards, Valentin Valchev On 17/09/2015 13:50, Jean-Baptiste Onofré wrote: > +1 (non binding) On 17/09/2015 15:02, David Bosschaert wrote: > +1 On 17/09/2015 15:51, Pierre De Rop wrote: > Hi; > > +1 On 19/09/2015 15:47, Carsten Ziegeler wrote: > +1 -- Mit freundlichen Grüßen / Best regards *Valentin Valchev* ProSyst Software GmbH Senior Project Manager Aachener Str. 222 50931 Cologne Germany _www.prosyst.com_ <http://www.prosyst.com> <https://twitter.com/ProSystSoftware> <https://www.linkedin.com/company/prosyst> <https://www.facebook.com/ProSyst.OSGI?fref=ts> Tel. +359 (0)2 952 35 81 Fax +359 (0)2 953 26 17 _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. Dimitar Valtchev signature.asc Description: OpenPGP digital signature
[VOTE RESULT] Release Felix webconsole-event-plugin version 1.1.4
Hi, The vote has passed with three binding +1 votes and one non-binding: +1 (binding): Carsten Ziegeler, David Bosschaert, Pierre De Rop +1 (non binding): Jean-Baptiste Onofré I would ask a member of the Apache Felix PMC to promote the release and upload artifacts to maven central. (http://felix.apache.org/documentation/development/release-management-nexus.html#promoting-the-release) Meanwhile, I'll fix the versions in the JIRA project. Regards, Valentin Valchev On 17/09/2015 17:07, Jean-Baptiste Onofré wrote: > +1 (non binding) On 17/09/2015 17:17, David Bosschaert wrote: > +1 On 19/09/2015 15:51, Carsten Ziegeler wrote: > +1 On 23/09/2015 14:05, Pierre De Rop wrote: > Hi Valentin; > > +1 -- Mit freundlichen Grüßen / Best regards *Valentin Valchev* ProSyst Software GmbH Senior Project Manager Aachener Str. 222 50931 Cologne Germany _www.prosyst.com_ <http://www.prosyst.com> <https://twitter.com/ProSystSoftware> <https://www.linkedin.com/company/prosyst> <https://www.facebook.com/ProSyst.OSGI?fref=ts> Tel. +359 (0)2 952 35 81 Fax +359 (0)2 953 26 17 _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. Dimitar Valtchev signature.asc Description: OpenPGP digital signature
[VOTE RESULT] Release Felix Web Console version 4.2.12
Hi, The vote has passed with three binding +1 votes and two non-binding: +1 (binding): Carsten Ziegeler, David Bosschaert, Pierre De Rop +1 (non binding): Jamie G, Jean-Baptiste Onofré I would ask a member of the Apache Felix PMC to promote the release and upload artifacts to maven central. (http://felix.apache.org/documentation/development/release-management-nexus.html#promoting-the-release) Meanwhile, I'll fix the versions in the JIRA project. Regards, Valentin Valchev On 18/09/2015 13:48, Jean-Baptiste Onofré wrote: > +1 (non binding) On 18/09/2015 14:17, Jamie G. wrote: > +1 (non-binding) On 18/09/2015 15:55, David Bosschaert wrote: > +1 On 19/09/2015 15:50, Carsten Ziegeler wrote: > +1 On 23/09/2015 14:06, Pierre De Rop wrote: > Hi; > > Verified signatures, did some basic tests, rebuilt the binaries from the source. > > +1 -- Mit freundlichen Grüßen / Best regards *Valentin Valchev* ProSyst Software GmbH Senior Project Manager Aachener Str. 222 50931 Cologne Germany _www.prosyst.com_ <http://www.prosyst.com> <https://twitter.com/ProSystSoftware> <https://www.linkedin.com/company/prosyst> <https://www.facebook.com/ProSyst.OSGI?fref=ts> Tel. +359 (0)2 952 35 81 Fax +359 (0)2 953 26 17 _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. Dimitar Valtchev signature.asc Description: OpenPGP digital signature
Re: [VOTE] Release Felix webconsole-event-plugin version 1.1.4
Hi, We need one more binding vote to release this module. Please, vote for it. Regards, Valentin On 17/09/2015 15:46, Valentin Valchev wrote: > Hi, > > I would like to release a new version of the webconsole-event-plugin module. > We solved 1 *major* issues in this release: > > ** Bug > * [FELIX-5025] - NPE in Events web console plugin - no events can be seen > > There are no outstanding issues. > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-1091 > > 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 1091 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > This vote will be open for 72 hours. > -- > > Mit freundlichen Grüßen / Best regards > > *Valentin Valchev* > > ProSyst Software GmbH > Senior Project Manager > Aachener Str. 222 > 50931 Cologne > Germany > > _www.prosyst.com_ <http://www.prosyst.com> > > <https://twitter.com/ProSystSoftware> > <https://www.linkedin.com/company/prosyst> > <https://www.facebook.com/ProSyst.OSGI?fref=ts> > > Tel. +359 (0)2 952 35 81 > Fax +359 (0)2 953 26 17 > _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> > > Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 > Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. > Dimitar Valtchev > -- Mit freundlichen Grüßen / Best regards *Valentin Valchev* ProSyst Software GmbH Senior Project Manager Aachener Str. 222 50931 Cologne Germany _www.prosyst.com_ <http://www.prosyst.com> <https://twitter.com/ProSystSoftware> <https://www.linkedin.com/company/prosyst> <https://www.facebook.com/ProSyst.OSGI?fref=ts> Tel. +359 (0)2 952 35 81 Fax +359 (0)2 953 26 17 _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. Dimitar Valtchev signature.asc Description: OpenPGP digital signature
Re: [VOTE] Release Felix Web Console version 4.2.12
Hello, We need just one binding vote to release the module. Please, vote. Regards, Valentin On 18/09/2015 10:36, Valentin Valchev wrote: > Hi, > > I would like to release the next version of Apache Felix Web Console. > We solved 9 issues in this release: > > ** Bug > * [FELIX-2880] - The Webconsole does not handle > Vector > * [FELIX-3366] - The Configuration Webconsole Plugin seems to > ignore the ocd ref element > * [FELIX-4849] - Do not call setContentLength after calling > sendRedirect > * [FELIX-4995] - NPE when updating Apache Felix OSGi Management > Console configuration without a password > * [FELIX-5004] - Null is passed to BundleInfoProvider if plugin > root is null > * [FELIX-5031] - NPE in Web Console configuration plugin when > metatype service is missing > * [FELIX-5041] - Cannot build web console with JDK 1.8 due to > javadoc problems > > ** Improvement > * [FELIX-5018] - [webconsole] "create factory configuration" link > for config screen > * [FELIX-5019] - [webconsole] "referer" parameter for > configuration open/create link > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-1093/ > > 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 1093 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > This vote will be open for 72 hours. > -- > > Mit freundlichen Grüßen / Best regards > > *Valentin Valchev* > > ProSyst Software GmbH > Senior Project Manager > Aachener Str. 222 > 50931 Cologne > Germany > > _www.prosyst.com_ <http://www.prosyst.com> > > <https://twitter.com/ProSystSoftware> > <https://www.linkedin.com/company/prosyst> > <https://www.facebook.com/ProSyst.OSGI?fref=ts> > > Tel. +359 (0)2 952 35 81 > Fax +359 (0)2 953 26 17 > _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> > > Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 > Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. > Dimitar Valtchev > -- Mit freundlichen Grüßen / Best regards *Valentin Valchev* ProSyst Software GmbH Senior Project Manager Aachener Str. 222 50931 Cologne Germany _www.prosyst.com_ <http://www.prosyst.com> <https://twitter.com/ProSystSoftware> <https://www.linkedin.com/company/prosyst> <https://www.facebook.com/ProSyst.OSGI?fref=ts> Tel. +359 (0)2 952 35 81 Fax +359 (0)2 953 26 17 _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. Dimitar Valtchev signature.asc Description: OpenPGP digital signature
[VOTE] Release Felix Web Console version 4.2.12
Hi, I would like to release the next version of Apache Felix Web Console. We solved 9 issues in this release: ** Bug * [FELIX-2880] - The Webconsole does not handle Vector * [FELIX-3366] - The Configuration Webconsole Plugin seems to ignore the ocd ref element * [FELIX-4849] - Do not call setContentLength after calling sendRedirect * [FELIX-4995] - NPE when updating Apache Felix OSGi Management Console configuration without a password * [FELIX-5004] - Null is passed to BundleInfoProvider if plugin root is null * [FELIX-5031] - NPE in Web Console configuration plugin when metatype service is missing * [FELIX-5041] - Cannot build web console with JDK 1.8 due to javadoc problems ** Improvement * [FELIX-5018] - [webconsole] "create factory configuration" link for config screen * [FELIX-5019] - [webconsole] "referer" parameter for configuration open/create link Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-1093/ 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 1093 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours. -- Mit freundlichen Grüßen / Best regards *Valentin Valchev* ProSyst Software GmbH Senior Project Manager Aachener Str. 222 50931 Cologne Germany _www.prosyst.com_ <http://www.prosyst.com> <https://twitter.com/ProSystSoftware> <https://www.linkedin.com/company/prosyst> <https://www.facebook.com/ProSyst.OSGI?fref=ts> Tel. +359 (0)2 952 35 81 Fax +359 (0)2 953 26 17 _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. Dimitar Valtchev signature.asc Description: OpenPGP digital signature
[jira] [Resolved] (FELIX-5041) Cannot build web console with JDK 1.8 due to javadoc problems
[
https://issues.apache.org/jira/browse/FELIX-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Valchev resolved FELIX-5041.
-
Resolution: Fixed
Fix Version/s: webconsole-4.2.12
fixed in svn
> Cannot build web console with JDK 1.8 due to javadoc problems
> -
>
> Key: FELIX-5041
> URL: https://issues.apache.org/jira/browse/FELIX-5041
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-4.2.10
> Reporter: Valentin Valchev
> Assignee: Valentin Valchev
> Fix For: webconsole-4.2.12
>
>
> Running "mvn javadoc:javadoc" fails with the following errors:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.2:javadoc (default-cli) on
> project org.apache.felix.webconsole: An error has o
> ccurred in JavaDocs report generation:
> [ERROR] Exit code: 1 - javadoc: warning - Multiple sources of package
> comments found for package "org.osgi.framework"
> [ERROR] javadoc: warning - Multiple sources of package comments found for
> package "org.osgi.service.packageadmin"
> [ERROR] javadoc: warning - Multiple sources of package comments found for
> package "org.osgi.service.startlevel"
> [ERROR]
> d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\AbstractWebConsolePlugin.java:210:
> error: unknown tag: true
> [ERROR] * true and may be overwritten by plugins to detect
> [ERROR] ^
> [ERROR]
> d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\AbstractWebConsolePlugin.java:215:
> warning: nested tag not allowed:
> [ERROR] * @return true if the page should have headers and
> footers rendered
> [ERROR] ^
> [ERROR]
> d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\AbstractWebConsolePlugin.java:210:
> error: element not closed: code
> [ERROR] * true and may be overwritten by plugins to detect
> [ERROR] ^
> [ERROR]
> d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\DefaultBrandingPlugin.java:84:
> error: no summary or caption for table
> [ERROR] *
> [ERROR] ^
> [ERROR]
> d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\DefaultVariableResolver.java:50:
> error: bad HTML entity
> [ERROR] * Creates a new variable resolver and initializes both - capacity &
> load factor
> [ERROR] ^
> [ERROR]
> d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\WebConsoleConstants.java:164:
> error: malformed HTML
> [ERROR] * The type of this request attribute is Map String>.
> [ERROR] ^
> [ERROR]
> d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\WebConsoleConstants.java:164:
> error: bad use of '>'
> [ERROR] * The type of this request attribute is Map String>.
> [ERROR] ^
> [ERROR]
> d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\WebConsoleUtil.java:254:
> error: malformed HTML
> [ERROR] * Escapes HTML special chars like: <>&\r\n and space
> [ERROR] ^
> [ERROR]
> d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\WebConsoleUtil.java:254:
> error: bad use of '>'
> [ERROR] * Escapes HTML special chars like: <>&\r\n and space
> [ERROR] ^
> [ERROR]
> d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\WebConsoleUtil.java:254:
> error: bad HTML entity
> [ERROR] * Escapes HTML special chars like: <>&\r\n and space
> [ERROR] ^
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FELIX-5041) Cannot build web console with JDK 1.8 due to javadoc problems
Valentin Valchev created FELIX-5041:
---
Summary: Cannot build web console with JDK 1.8 due to javadoc
problems
Key: FELIX-5041
URL: https://issues.apache.org/jira/browse/FELIX-5041
Project: Felix
Issue Type: Bug
Components: Web Console
Affects Versions: webconsole-4.2.10
Reporter: Valentin Valchev
Assignee: Valentin Valchev
Running "mvn javadoc:javadoc" fails with the following errors:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:2.10.2:javadoc (default-cli) on
project org.apache.felix.webconsole: An error has o
ccurred in JavaDocs report generation:
[ERROR] Exit code: 1 - javadoc: warning - Multiple sources of package comments
found for package "org.osgi.framework"
[ERROR] javadoc: warning - Multiple sources of package comments found for
package "org.osgi.service.packageadmin"
[ERROR] javadoc: warning - Multiple sources of package comments found for
package "org.osgi.service.startlevel"
[ERROR]
d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\AbstractWebConsolePlugin.java:210:
error: unknown tag: true
[ERROR] * true and may be overwritten by plugins to detect
[ERROR] ^
[ERROR]
d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\AbstractWebConsolePlugin.java:215:
warning: nested tag not allowed:
[ERROR] * @return true if the page should have headers and footers
rendered
[ERROR] ^
[ERROR]
d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\AbstractWebConsolePlugin.java:210:
error: element not closed: code
[ERROR] * true and may be overwritten by plugins to detect
[ERROR] ^
[ERROR]
d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\DefaultBrandingPlugin.java:84:
error: no summary or caption for table
[ERROR] *
[ERROR] ^
[ERROR]
d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\DefaultVariableResolver.java:50:
error: bad HTML entity
[ERROR] * Creates a new variable resolver and initializes both - capacity &
load factor
[ERROR] ^
[ERROR]
d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\WebConsoleConstants.java:164:
error: malformed HTML
[ERROR] * The type of this request attribute is Map.
[ERROR] ^
[ERROR]
d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\WebConsoleConstants.java:164:
error: bad use of '>'
[ERROR] * The type of this request attribute is Map.
[ERROR] ^
[ERROR]
d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\WebConsoleUtil.java:254:
error: malformed HTML
[ERROR] * Escapes HTML special chars like: <>&\r\n and space
[ERROR] ^
[ERROR]
d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\WebConsoleUtil.java:254:
error: bad use of '>'
[ERROR] * Escapes HTML special chars like: <>&\r\n and space
[ERROR] ^
[ERROR]
d:\develop\.apache-felix\webconsole\src\main\java\org\apache\felix\webconsole\WebConsoleUtil.java:254:
error: bad HTML entity
[ERROR] * Escapes HTML special chars like: <>&\r\n and space
[ERROR] ^
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[VOTE] Release Felix webconsole-event-plugin version 1.1.4
Hi, I would like to release a new version of the webconsole-event-plugin module. We solved 1 *major* issues in this release: ** Bug * [FELIX-5025] - NPE in Events web console plugin - no events can be seen There are no outstanding issues. Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-1091 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 1091 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours. -- Mit freundlichen Grüßen / Best regards *Valentin Valchev* ProSyst Software GmbH Senior Project Manager Aachener Str. 222 50931 Cologne Germany _www.prosyst.com_ <http://www.prosyst.com> <https://twitter.com/ProSystSoftware> <https://www.linkedin.com/company/prosyst> <https://www.facebook.com/ProSyst.OSGI?fref=ts> Tel. +359 (0)2 952 35 81 Fax +359 (0)2 953 26 17 _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. Dimitar Valtchev signature.asc Description: OpenPGP digital signature
[VOTE] Release Felix webconsole-packageadmin-plugin version 1.0.2
Hi, I would like to release a new version of the webconsole-packageadmin-plugin module. We solved 5 issues in this release: Here is a list of changes: * [FELIX-3968] - StringIndexOutOfBoundsException in packageadmin plugin * [FELIX-4996] - Dependency Finder should use Inventory instead of deprecated ConfigurationPrinter ** Improvement * [FELIX-3656] - Change the label for the dependency finder plugin to "Dependency Finder" from "Packages" * [FELIX-3861] - Set felix.webconsole.category on Web Console plugins * [FELIX-4430] - [PackageAdmin Web Console Plugin] Provide using bundles with versions Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-1090/ 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 1089 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours. -- Mit freundlichen Grüßen / Best regards *Valentin Valchev* ProSyst Software GmbH Senior Project Manager Aachener Str. 222 50931 Cologne Germany _www.prosyst.com_ <http://www.prosyst.com> <https://twitter.com/ProSystSoftware> <https://www.linkedin.com/company/prosyst> <https://www.facebook.com/ProSyst.OSGI?fref=ts> Tel. +359 (0)2 952 35 81 Fax +359 (0)2 953 26 17 _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. Dimitar Valtchev signature.asc Description: OpenPGP digital signature
[jira] [Comment Edited] (FELIX-5019) [webconsole] "referer" parameter for configuration open/create link
[
https://issues.apache.org/jira/browse/FELIX-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14768856#comment-14768856
]
Valentin Valchev edited comment on FELIX-5019 at 9/16/15 12:47 PM:
---
When I download the patch it actually tries to patch the ConfigManager.java
twice. It's the same some other files and Eclipse is still unable to apply it.
I've also tried with the patch command, but it also fails.
was (Author: v_valchev):
When I download the patch it actually tries to path the ConfigManager.java
twice. It's the same some other files and Eclipse is still unable to apply it.
I've also tried with the patch command, but it also fails.
> [webconsole] "referer" parameter for configuration open/create link
> ---
>
> Key: FELIX-5019
> URL: https://issues.apache.org/jira/browse/FELIX-5019
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: webconsole-4.2.10
> Reporter: Balazs Zsoldos
>Assignee: Valentin Valchev
> Fix For: webconsole-4.2.12
>
>
> It is possible to open/create configuration by linking the configuration
> screen with the following format:
> {code}
> /system/console/configMgr/configurationPid
> {code}
> I propose a new parameter that can tell where to redirect after the
> configuration dialog is closed. E.g.:
> {code}
> /system/console/configMgr/configurationPid?referer=/system/console/componentView
> {code}
> If you like this proposal, pull request comes within 1-2 days.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (FELIX-5019) [webconsole] "referer" parameter for configuration open/create link
[
https://issues.apache.org/jira/browse/FELIX-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Valchev resolved FELIX-5019.
-
Resolution: Fixed
Assignee: Valentin Valchev
Fix Version/s: webconsole-4.2.12
Ok, I've used the 36.diff instead of the patch and it's all right now.
So it's fixed in SVN rev.1703394.
> [webconsole] "referer" parameter for configuration open/create link
> ---
>
> Key: FELIX-5019
> URL: https://issues.apache.org/jira/browse/FELIX-5019
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: webconsole-4.2.10
> Reporter: Balazs Zsoldos
>Assignee: Valentin Valchev
> Fix For: webconsole-4.2.12
>
>
> It is possible to open/create configuration by linking the configuration
> screen with the following format:
> {code}
> /system/console/configMgr/configurationPid
> {code}
> I propose a new parameter that can tell where to redirect after the
> configuration dialog is closed. E.g.:
> {code}
> /system/console/configMgr/configurationPid?referer=/system/console/componentView
> {code}
> If you like this proposal, pull request comes within 1-2 days.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FELIX-5019) [webconsole] "referer" parameter for configuration open/create link
[
https://issues.apache.org/jira/browse/FELIX-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14768856#comment-14768856
]
Valentin Valchev commented on FELIX-5019:
-
When I download the patch it actually tries to path the ConfigManager.java
twice. It's the same some other files and Eclipse is still unable to apply it.
I've also tried with the patch command, but it also fails.
> [webconsole] "referer" parameter for configuration open/create link
> ---
>
> Key: FELIX-5019
> URL: https://issues.apache.org/jira/browse/FELIX-5019
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: webconsole-4.2.10
>Reporter: Balazs Zsoldos
>
> It is possible to open/create configuration by linking the configuration
> screen with the following format:
> {code}
> /system/console/configMgr/configurationPid
> {code}
> I propose a new parameter that can tell where to redirect after the
> configuration dialog is closed. E.g.:
> {code}
> /system/console/configMgr/configurationPid?referer=/system/console/componentView
> {code}
> If you like this proposal, pull request comes within 1-2 days.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [VOTE] Release Apache Felix DS WebConsole Plugin
+1 (non binding) On 16/09/2015 11:55, Carsten Ziegeler wrote: > I would like to call a vote on the following subproject release: > > ds webconsole plugin 2.0.2 > > We solved three issues: > https://issues.apache.org/jira/browse/FELIX/fixforversion/12333162 > > Staging repositories: > https://repository.apache.org/content/repositories/orgapachefelix-1089/ > > 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 1089 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > Carsten -- Mit freundlichen Grüßen / Best regards *Valentin Valchev* ProSyst Software GmbH Senior Project Manager Aachener Str. 222 50931 Cologne Germany _www.prosyst.com_ <http://www.prosyst.com> <https://twitter.com/ProSystSoftware> <https://www.linkedin.com/company/prosyst> <https://www.facebook.com/ProSyst.OSGI?fref=ts> Tel. +359 (0)2 952 35 81 Fax +359 (0)2 953 26 17 _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. Dimitar Valtchev signature.asc Description: OpenPGP digital signature
[jira] [Commented] (FELIX-5019) [webconsole] "referer" parameter for configuration open/create link
[
https://issues.apache.org/jira/browse/FELIX-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741936#comment-14741936
]
Valentin Valchev commented on FELIX-5019:
-
IMHO this feature would be very convenient if you want to edit the
configuration from another plugin, so I like it.
I would like to merge your path too, but after applying your previous one, this
one has conflicts. And I'm not using git, and I don't have too much time to
spend on that.
So if you provide a new patch, that can be cleanly applied on the current
webconsole code, I will certainly merge it.
> [webconsole] "referer" parameter for configuration open/create link
> ---
>
> Key: FELIX-5019
> URL: https://issues.apache.org/jira/browse/FELIX-5019
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: webconsole-4.2.10
>Reporter: Balazs Zsoldos
>
> It is possible to open/create configuration by linking the configuration
> screen with the following format:
> {code}
> /system/console/configMgr/configurationPid
> {code}
> I propose a new parameter that can tell where to redirect after the
> configuration dialog is closed. E.g.:
> {code}
> /system/console/configMgr/configurationPid?referer=/system/console/componentView
> {code}
> If you like this proposal, pull request comes within 1-2 days.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (FELIX-5031) NPE in Web Console configuration plugin when metatype service is missing
[
https://issues.apache.org/jira/browse/FELIX-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Valchev resolved FELIX-5031.
-
Resolution: Fixed
Fix Version/s: webconsole-4.2.12
Fixed in svn r1702457
> NPE in Web Console configuration plugin when metatype service is missing
>
>
> Key: FELIX-5031
> URL: https://issues.apache.org/jira/browse/FELIX-5031
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-4.2.10
> Reporter: Valentin Valchev
> Assignee: Valentin Valchev
>Priority: Critical
> Fix For: webconsole-4.2.12
>
>
> The following exception occurs when metatype service is missing:
> {code}
> java.lang.NullPointerException
> at
> org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.getConfigurationPropertyValueOrDefault(ConfigAdminSupport.java:703)
> at
> org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.getConfigurationFactoryNameHint(ConfigAdminSupport.java:641)
> at
> org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.listConfigurations(ConfigAdminSupport.java:608)
> at
> org.apache.felix.webconsole.internal.configuration.ConfigManager.renderContent(ConfigManager.java:395)
> at
> org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:194)
> at
> org.apache.felix.webconsole.internal.configuration.ConfigManager.doGet(ConfigManager.java:330)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at
> org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:567)
> at
> org.apache.felix.webconsole.internal.servlet.OsgiManager$3.run(OsgiManager.java:465)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:461)
> {code}
> This is probably related to FELIX-4710
> As result all configurations are missing and the plugin becomes completely
> unusable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FELIX-5031) NPE in Web Console configuration plugin when metatype service is missing
Valentin Valchev created FELIX-5031:
---
Summary: NPE in Web Console configuration plugin when metatype
service is missing
Key: FELIX-5031
URL: https://issues.apache.org/jira/browse/FELIX-5031
Project: Felix
Issue Type: Bug
Components: Web Console
Affects Versions: webconsole-4.2.10
Reporter: Valentin Valchev
Assignee: Valentin Valchev
Priority: Critical
The following exception occurs when metatype service is missing:
{code}
java.lang.NullPointerException
at
org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.getConfigurationPropertyValueOrDefault(ConfigAdminSupport.java:703)
at
org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.getConfigurationFactoryNameHint(ConfigAdminSupport.java:641)
at
org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.listConfigurations(ConfigAdminSupport.java:608)
at
org.apache.felix.webconsole.internal.configuration.ConfigManager.renderContent(ConfigManager.java:395)
at
org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:194)
at
org.apache.felix.webconsole.internal.configuration.ConfigManager.doGet(ConfigManager.java:330)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:567)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager$3.run(OsgiManager.java:465)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:461)
{code}
As result all configurations are missing and the plugin becomes completely
unusable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-5031) NPE in Web Console configuration plugin when metatype service is missing
[
https://issues.apache.org/jira/browse/FELIX-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Valchev updated FELIX-5031:
Description:
The following exception occurs when metatype service is missing:
{code}
java.lang.NullPointerException
at
org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.getConfigurationPropertyValueOrDefault(ConfigAdminSupport.java:703)
at
org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.getConfigurationFactoryNameHint(ConfigAdminSupport.java:641)
at
org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.listConfigurations(ConfigAdminSupport.java:608)
at
org.apache.felix.webconsole.internal.configuration.ConfigManager.renderContent(ConfigManager.java:395)
at
org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:194)
at
org.apache.felix.webconsole.internal.configuration.ConfigManager.doGet(ConfigManager.java:330)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:567)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager$3.run(OsgiManager.java:465)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:461)
{code}
This is probably related to FELIX-4710
As result all configurations are missing and the plugin becomes completely
unusable.
was:
The following exception occurs when metatype service is missing:
{code}
java.lang.NullPointerException
at
org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.getConfigurationPropertyValueOrDefault(ConfigAdminSupport.java:703)
at
org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.getConfigurationFactoryNameHint(ConfigAdminSupport.java:641)
at
org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.listConfigurations(ConfigAdminSupport.java:608)
at
org.apache.felix.webconsole.internal.configuration.ConfigManager.renderContent(ConfigManager.java:395)
at
org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:194)
at
org.apache.felix.webconsole.internal.configuration.ConfigManager.doGet(ConfigManager.java:330)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:567)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager$3.run(OsgiManager.java:465)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:461)
{code}
As result all configurations are missing and the plugin becomes completely
unusable.
> NPE in Web Console configuration plugin when metatype service is missing
>
>
> Key: FELIX-5031
> URL: https://issues.apache.org/jira/browse/FELIX-5031
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-4.2.10
> Reporter: Valentin Valchev
> Assignee: Valentin Valchev
>Priority: Critical
>
> The following exception occurs when metatype service is missing:
> {code}
> java.lang.NullPointerException
> at
> org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.getConfigurationPropertyValueOrDefault(ConfigAdminSupport.java:703)
> at
> org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.getConfigurationFactoryNameHint(ConfigAdminSupport.java:641)
> at
> org.apache.felix.webconsole.internal.configuration.ConfigAdminSupport.listConfigurations(ConfigAdminSupport.java:608)
> at
> org.apache.felix.webconsole.internal.configuration.ConfigManager.renderContent(ConfigManager.java:395)
> at
> org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:194)
> at
> org.apache.felix.webconsole.internal.configuration.ConfigManager.doGet(ConfigManager.java:330)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at
> org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:567)
> at
> org.apache.felix.webconsole.internal.servlet.OsgiMana
[jira] [Resolved] (FELIX-3366) The Configuration Webconsole Plugin seems to ignore the ocd ref element
[ https://issues.apache.org/jira/browse/FELIX-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-3366. - Resolution: Fixed Fix Version/s: webconsole-4.2.12 There is a test case now, that proves the problem is fixed some time ago. Since I don't know when, I'm going to set this issue fixed for the next version of webconsole. > The Configuration Webconsole Plugin seems to ignore the ocd ref element > --- > > Key: FELIX-3366 > URL: https://issues.apache.org/jira/browse/FELIX-3366 > Project: Felix > Issue Type: Bug > Components: Web Console > Environment: Equinox container with apache felix webadmin, http und > metatype bundle >Reporter: Christoph Läubrich >Priority: Minor > Fix For: webconsole-4.2.12 > > Attachments: TEST-FELIX-3366.jar > > > If there is a desiginator like this: > > > > > everythiong works fine. > Using something different ad the OCD Id than the pid makes the webconsole > plugin thing there is no OCD at all (it just provides a textfield where you > can enter the properties by name): > > > > > maybe I get something wrong but I can't see from the spec that the pid must > equal the ocd id (in fact the examples does alwys use a different name) the > metatype service itself has not any problem with both notations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-3366) The Configuration Webconsole Plugin seems to ignore the ocd ref element
[ https://issues.apache.org/jira/browse/FELIX-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev updated FELIX-3366: Attachment: TEST-FELIX-3366.jar The attached bundle create a metatype xml, which is similar to the one provided. With the latest web console and metatype service it works just as expected. > The Configuration Webconsole Plugin seems to ignore the ocd ref element > --- > > Key: FELIX-3366 > URL: https://issues.apache.org/jira/browse/FELIX-3366 > Project: Felix > Issue Type: Bug > Components: Web Console > Environment: Equinox container with apache felix webadmin, http und > metatype bundle >Reporter: Christoph Läubrich >Priority: Minor > Attachments: TEST-FELIX-3366.jar > > > If there is a desiginator like this: > > > > > everythiong works fine. > Using something different ad the OCD Id than the pid makes the webconsole > plugin thing there is no OCD at all (it just provides a textfield where you > can enter the properties by name): > > > > > maybe I get something wrong but I can't see from the spec that the pid must > equal the ocd id (in fact the examples does alwys use a different name) the > metatype service itself has not any problem with both notations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-2880) The Webconsole does not handle Vector
[ https://issues.apache.org/jira/browse/FELIX-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-2880. - Resolution: Fixed Fix Version/s: webconsole-4.2.12 webconsole v4.2.12 is verified, that works correctly the problem is probably fixed long ago, but now we have a test bundle, that proves it's fixed. > The Webconsole does not handle Vector > --- > > Key: FELIX-2880 > URL: https://issues.apache.org/jira/browse/FELIX-2880 > Project: Felix > Issue Type: Bug > Components: Web Console >Reporter: Peter Kriens > Fix For: webconsole-4.2.12 > > Attachments: TEST-FELIX-2880.jar > > > An AD like: > type='Integer'/> > Should be edited as a list and returned as a Vector. However, this > shows as a single integer in the webconsole, not a list editor. I guess it > gets confused with primiitves? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-2880) The Webconsole does not handle Vector
[ https://issues.apache.org/jira/browse/FELIX-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev updated FELIX-2880: Attachment: TEST-FELIX-2880.jar The attached test bundle proves, that the problem doesn't exist with the latest webconsole. > The Webconsole does not handle Vector > --- > > Key: FELIX-2880 > URL: https://issues.apache.org/jira/browse/FELIX-2880 > Project: Felix > Issue Type: Bug > Components: Web Console >Reporter: Peter Kriens > Attachments: TEST-FELIX-2880.jar > > > An AD like: > type='Integer'/> > Should be edited as a list and returned as a Vector. However, this > shows as a single integer in the webconsole, not a list editor. I guess it > gets confused with primiitves? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-5018) [webconsole] "create factory configuration" link for config screen
[
https://issues.apache.org/jira/browse/FELIX-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Valchev resolved FELIX-5018.
-
Resolution: Fixed
Assignee: Valentin Valchev
Fix Version/s: webconsole-4.2.12
Hello Balazs,
I've just applied your path in svn r1702443
> [webconsole] "create factory configuration" link for config screen
> --
>
> Key: FELIX-5018
> URL: https://issues.apache.org/jira/browse/FELIX-5018
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
>Affects Versions: webconsole-4.2.10
>Reporter: Balazs Zsoldos
>Assignee: Valentin Valchev
> Fix For: webconsole-4.2.12
>
>
> At the moment, it is possible to create a link to the configuration screen
> that:
> * opens an existing configuration
> * creates a non-factory configuration if it does not exist yet
> It would be nice to be able to create a link that can be used to create
> configuration for factories.
> At the moment can look like this:
> {code}
> /system/console/configMgr/myPid
> {code}
> We propose the _factoryCreate_ parameter. When it is true, a new
> configuration will be created for that factory. The link could be used like
> this:
> {code}
> /system/console/configMgr/myPid?factoryCreate=true
> {code}
> If you agree, the pull request will come within 1-2 days.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (FELIX-5026) Web Console Event plugin exception when sending event with property of type hex/base64
[
https://issues.apache.org/jira/browse/FELIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Valchev resolved FELIX-5026.
-
Resolution: Fixed
fixed in svn r1701216
I've actually removed the hex/base64/sha1 support. It was a little weird to
send hashes over event admin. If it is really a password hash, the event admin
is not the a secure way to provide it to some other component(s).
Instead I've added support for 'byte array'. And it handles different formats
of those byte arrays. All those variants are accepted:
"0, 03, 0xfa, #40"
"{10,23,32}"
"[30,33,33]"
"00:00:00:00"
> Web Console Event plugin exception when sending event with property of type
> hex/base64
> --
>
> Key: FELIX-5026
> URL: https://issues.apache.org/jira/browse/FELIX-5026
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-event-plugin-1.1.2
>Reporter: Valentin Valchev
>Assignee: Valentin Valchev
>
> base64/hex/sha1 types are basically unsupported by the java code, but the UI
> renders them as supported types:
> {code}
> java.lang.IllegalArgumentException: Unsupported type!
> at
> org.apache.felix.webconsole.plugins.event.internal.PropertiesEditorSupport.convert(PropertiesEditorSupport.java:90)
> at
> org.apache.felix.webconsole.plugins.event.internal.PropertiesEditorSupport.convertProperties(PropertiesEditorSupport.java:51)
> at
> org.apache.felix.webconsole.plugins.event.internal.PluginServlet.newEvent(PluginServlet.java:109)
> at
> org.apache.felix.webconsole.plugins.event.internal.PluginServlet.doPost(PluginServlet.java:121)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at
> org.apache.felix.webconsole.internal.WebConsolePluginAdapter.service(WebConsolePluginAdapter.java:216)
> at
> org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:567)
> at
> org.apache.felix.webconsole.internal.servlet.OsgiManager$3.run(OsgiManager.java:465)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:461)
> at
> com.prosyst.mbs.impl.services.http.ServletProperties.service(ServletProperties.java:109)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FELIX-5026) Web Console Event plugin exception when sending event with property of type hex/base64
Valentin Valchev created FELIX-5026:
---
Summary: Web Console Event plugin exception when sending event
with property of type hex/base64
Key: FELIX-5026
URL: https://issues.apache.org/jira/browse/FELIX-5026
Project: Felix
Issue Type: Bug
Components: Web Console
Affects Versions: webconsole-event-plugin-1.1.2
Reporter: Valentin Valchev
Assignee: Valentin Valchev
base64/hex/sha1 types are basically unsupported by the java code, but the UI
renders them as supported types:
{code}
java.lang.IllegalArgumentException: Unsupported type!
at
org.apache.felix.webconsole.plugins.event.internal.PropertiesEditorSupport.convert(PropertiesEditorSupport.java:90)
at
org.apache.felix.webconsole.plugins.event.internal.PropertiesEditorSupport.convertProperties(PropertiesEditorSupport.java:51)
at
org.apache.felix.webconsole.plugins.event.internal.PluginServlet.newEvent(PluginServlet.java:109)
at
org.apache.felix.webconsole.plugins.event.internal.PluginServlet.doPost(PluginServlet.java:121)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.apache.felix.webconsole.internal.WebConsolePluginAdapter.service(WebConsolePluginAdapter.java:216)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:567)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager$3.run(OsgiManager.java:465)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:461)
at
com.prosyst.mbs.impl.services.http.ServletProperties.service(ServletProperties.java:109)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (FELIX-4849) Do not call setContentLength after calling sendRedirect
[ https://issues.apache.org/jira/browse/FELIX-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-4849. - Resolution: Fixed Assignee: Valentin Valchev Fix Version/s: webconsole-4.2.12 fixed in svn r1701212 > Do not call setContentLength after calling sendRedirect > --- > > Key: FELIX-4849 > URL: https://issues.apache.org/jira/browse/FELIX-4849 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-4.2.8 > Environment: All >Reporter: Thomas Watson > Assignee: Valentin Valchev > Fix For: webconsole-4.2.12 > > > Calling setContentLength(0) after calling sendRedirect(path) is unnecessary > and usually results in an error message getting logged by the container. In > FELIX-3006 a call to setContentLength(0) was added to line 523 of the method > OsgiManager.service(HttpServletRequest, HttpServletResponse) > response.sendRedirect(path); > response.setContentLength(0); > The sendRedirect method commits the response so there is no benefit to trying > to call setContentLength because that attempts to set the Content-Length > header which cannot happen after a response has been committed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-5025) NPE in Events web console plugin - no events can be seen
[
https://issues.apache.org/jira/browse/FELIX-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Valchev resolved FELIX-5025.
-
Resolution: Fixed
Fix Version/s: webconsole-event-plugin-1.1.4
> NPE in Events web console plugin - no events can be seen
>
>
> Key: FELIX-5025
> URL: https://issues.apache.org/jira/browse/FELIX-5025
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-event-plugin-1.1.2
> Reporter: Valentin Valchev
> Assignee: Valentin Valchev
> Fix For: webconsole-event-plugin-1.1.4
>
>
> The following exception is seen when clicking on the Web Console Events
> plugin.
> {code}
> java.lang.NullPointerException
> at
> org.apache.felix.webconsole.plugins.event.internal.PluginServlet.eventJson(PluginServlet.java:373)
> at
> org.apache.felix.webconsole.plugins.event.internal.PluginServlet.renderJSON(PluginServlet.java:184)
> at
> org.apache.felix.webconsole.plugins.event.internal.PluginServlet.doGet(PluginServlet.java:208)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.apache.felix.webconsole.internal.WebConsolePluginAdapter.renderContent(WebConsolePluginAdapter.java:123)
> at
> org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:170)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.apache.felix.webconsole.internal.WebConsolePluginAdapter.service(WebConsolePluginAdapter.java:211)
> at
> org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:493)
> at
> org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:418)
> {code}
> I think the exception is caused due to an event, containing a property with
> value which is of type Array and one of the elements of the array is null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FELIX-5025) NPE in Events web console plugin - no events can be seen
Valentin Valchev created FELIX-5025:
---
Summary: NPE in Events web console plugin - no events can be seen
Key: FELIX-5025
URL: https://issues.apache.org/jira/browse/FELIX-5025
Project: Felix
Issue Type: Bug
Components: Web Console
Affects Versions: webconsole-event-plugin-1.1.2
Reporter: Valentin Valchev
Assignee: Valentin Valchev
The following exception is seen when clicking on the Web Console Events plugin.
{code}
java.lang.NullPointerException
at
org.apache.felix.webconsole.plugins.event.internal.PluginServlet.eventJson(PluginServlet.java:373)
at
org.apache.felix.webconsole.plugins.event.internal.PluginServlet.renderJSON(PluginServlet.java:184)
at
org.apache.felix.webconsole.plugins.event.internal.PluginServlet.doGet(PluginServlet.java:208)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at
org.apache.felix.webconsole.internal.WebConsolePluginAdapter.renderContent(WebConsolePluginAdapter.java:123)
at
org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:170)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at
org.apache.felix.webconsole.internal.WebConsolePluginAdapter.service(WebConsolePluginAdapter.java:211)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:493)
at
org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:418)
{code}
I think the exception is caused due to an event, containing a property with
value which is of type Array and one of the elements of the array is null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: svn commit: r1694520 - /felix/trunk/org.apache.felix.webconsole/
Oh my god! That is the stupid Eclipse!! I just wanted to enable SVN access on my project. I didn't even attempted to commit anything! Sorry On 07/08/2015 02:56, Carsten Ziegeler wrote: > Hi Valentin, > > was this change intentional? We should not have a project twice in the > root. I don't mind using the full artifact id though > > Carsten > > Am 06.08.15 um 10:11 schrieb vvalc...@apache.org: >> Author: vvalchev >> Date: Thu Aug 6 15:11:42 2015 >> New Revision: 1694520 >> >> URL: http://svn.apache.org/r1694520 >> Log: >> Share project "org.apache.felix.webconsole" into >> "https://svn.apache.org/repos/asf/felix/trunk"; >> >> Added: >> felix/trunk/org.apache.felix.webconsole/ >> >> > -- Mit freundlichen Grüßen / Best regards *Valentin Valchev* ProSyst Software GmbH Senior Project Manager Aachener Str. 222 50931 Cologne Germany _www.prosyst.com_ <http://www.prosyst.com> <https://twitter.com/ProSystSoftware> <https://www.linkedin.com/company/prosyst> <https://www.facebook.com/ProSyst.OSGI?fref=ts> Tel. +359 (0)2 952 35 81 Fax +359 (0)2 953 26 17 _v.valchev@prosyst.bg_ <mailto:v.valc...@prosyst.bg> Registered office: Köln, Register court: Amtsgericht Köln HRB 54586 Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. Dimitar Valtchev signature.asc Description: OpenPGP digital signature
[jira] [Resolved] (FELIX-4998) Declarative Service plugin might provide JSON format support for Inventory Printer
[ https://issues.apache.org/jira/browse/FELIX-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-4998. - Resolution: Fixed implemented by svn commit: r1694680 > Declarative Service plugin might provide JSON format support for Inventory > Printer > -- > > Key: FELIX-4998 > URL: https://issues.apache.org/jira/browse/FELIX-4998 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-ds-plugin-2.0.2 > Reporter: Valentin Valchev > Assignee: Valentin Valchev >Priority: Minor > Fix For: webconsole-ds-plugin-2.0.2 > > > There is already support for JSON format in the plugin itself, so it should > be fairly easy to add json format to the printer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4998) Declarative Service plugin might provide JSON format support for Inventory Printer
Valentin Valchev created FELIX-4998: --- Summary: Declarative Service plugin might provide JSON format support for Inventory Printer Key: FELIX-4998 URL: https://issues.apache.org/jira/browse/FELIX-4998 Project: Felix Issue Type: Improvement Components: Web Console Affects Versions: webconsole-ds-plugin-2.0.2 Reporter: Valentin Valchev Assignee: Valentin Valchev Priority: Minor Fix For: webconsole-ds-plugin-2.0.2 There is already support for JSON format in the plugin itself, so it should be fairly easy to add json format to the printer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4997) UPnP plugin should use Inventory instead of deprecated ConfigurationPrinter
[ https://issues.apache.org/jira/browse/FELIX-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-4997. - Resolution: Fixed fixed in svn commit: r1694640 > UPnP plugin should use Inventory instead of deprecated ConfigurationPrinter > --- > > Key: FELIX-4997 > URL: https://issues.apache.org/jira/browse/FELIX-4997 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-upnp-plugin-1.0.6 > Reporter: Valentin Valchev > Assignee: Valentin Valchev >Priority: Minor > Fix For: webconsole-upnp-plugin-1.0.8 > > > Now it uses the ConfigurationPrinter but still I'm unable to see the UPnP > status for some reason. > The updated printer should also support both - text and json format of the > data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4997) UPnP plugin should use Inventory instead of deprecated ConfigurationPrinter
Valentin Valchev created FELIX-4997: --- Summary: UPnP plugin should use Inventory instead of deprecated ConfigurationPrinter Key: FELIX-4997 URL: https://issues.apache.org/jira/browse/FELIX-4997 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-upnp-plugin-1.0.6 Reporter: Valentin Valchev Assignee: Valentin Valchev Priority: Minor Fix For: webconsole-upnp-plugin-1.0.8 Now it uses the ConfigurationPrinter but still I'm unable to see the UPnP status for some reason. The updated printer should also support both - text and json format of the data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4996) Dependency Finder should use Inventory instead of deprecated ConfigurationPrinter
[ https://issues.apache.org/jira/browse/FELIX-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-4996. - Resolution: Fixed Fix Version/s: webconsole-packageadmin-plugin 1.0.2 svn commit: r1694635 > Dependency Finder should use Inventory instead of deprecated > ConfigurationPrinter > - > > Key: FELIX-4996 > URL: https://issues.apache.org/jira/browse/FELIX-4996 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-packageadmin-plugin 1.0.0 > Reporter: Valentin Valchev > Assignee: Valentin Valchev >Priority: Minor > Fix For: webconsole-packageadmin-plugin 1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4996) Dependency Finder should use Inventory instead of deprecated ConfigurationPrinter
Valentin Valchev created FELIX-4996: --- Summary: Dependency Finder should use Inventory instead of deprecated ConfigurationPrinter Key: FELIX-4996 URL: https://issues.apache.org/jira/browse/FELIX-4996 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-packageadmin-plugin 1.0.0 Reporter: Valentin Valchev Assignee: Valentin Valchev Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-3656) Change the label for the dependency finder plugin to "Dependency Finder" from "Packages"
[ https://issues.apache.org/jira/browse/FELIX-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-3656. - Resolution: Fixed Assignee: Valentin Valchev Fix Version/s: webconsole-packageadmin-plugin 1.0.2 fixed in svn commit: r1694631 - actually renamed it to Package Dependencies, not 'Dependency Finder' - set it correctly to the OSGi category as actually shows who provides and who uses the packages (e.g. Package Admin functionality) - updated the pom.xml and now you can correctly import the project into Eclipse > Change the label for the dependency finder plugin to "Dependency Finder" from > "Packages" > > > Key: FELIX-3656 > URL: https://issues.apache.org/jira/browse/FELIX-3656 > Project: Felix > Issue Type: Improvement > Components: Web Console > Reporter: Chetan Mehrotra >Assignee: Valentin Valchev >Priority: Trivial > Fix For: webconsole-packageadmin-plugin 1.0.2 > > > The label for the dependency finder webconsole plugin [1] is currently set to > "Packages" which does not convey its true utility!!. It would be helpful if > it is set to "Dependency Finder". > [1] > https://github.com/apache/felix/tree/trunk/webconsole-plugins/packageadmin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4995) NPE when updating Apache Felix OSGi Management Console configuration without a password
[
https://issues.apache.org/jira/browse/FELIX-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Valchev resolved FELIX-4995.
-
Resolution: Fixed
Assignee: Valentin Valchev
Fix Version/s: webconsole-4.2.12
fixed in svn commit: r1694628
> NPE when updating Apache Felix OSGi Management Console configuration without
> a password
> ---
>
> Key: FELIX-4995
> URL: https://issues.apache.org/jira/browse/FELIX-4995
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-4.2.10
> Reporter: Valentin Valchev
> Assignee: Valentin Valchev
> Fix For: webconsole-4.2.12
>
>
> The following exception occurs, when you try to save the webconsole
> configuration from the web console config plugin:
> {code}
> java.lang.NullPointerException
>
> java.security.MessageDigest$Delegate(java.security.MessageDigest).update(byte[])
> line: 293
>
> java.security.MessageDigest$Delegate(java.security.MessageDigest).digest(byte[])
> line: 368
>
> org.apache.felix.webconsole.internal.servlet.Password.hashPassword(byte[],
> java.lang.String) line: 178
>
> org.apache.felix.webconsole.internal.servlet.Password.hashPassword(java.lang.String,
> byte[]) line: 118
>
> org.apache.felix.webconsole.internal.servlet.Password.hashPassword(java.lang.String)
> line: 77
> {code}
> The implementation obviously expects password to be always set.
> However initially the configuration doesn't exist and when you create it with
> web console, the password is not set yet.
> However, if you do not edit the password in the configuration dialog, it is
> set to a PASSWORD_PLACEHOLDER_VALUE = "unmodifed".
> Then the following code becomes the reason of the problem, because of the
> incorrect assumption:
> {code}
> // assumption: config is not null and as a non-null password String property
> final String pwd = ( String ) config.get( OsgiManager.PROP_PASSWORD );
> final String hashedPassword = Password.hashPassword( pwd );
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-4995) NPE when updating Apache Felix OSGi Management Console configuration without a password
[
https://issues.apache.org/jira/browse/FELIX-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Valchev updated FELIX-4995:
Affects Version/s: (was: webconsole-4.2.8)
webconsole-4.2.10
> NPE when updating Apache Felix OSGi Management Console configuration without
> a password
> ---
>
> Key: FELIX-4995
> URL: https://issues.apache.org/jira/browse/FELIX-4995
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-4.2.10
> Reporter: Valentin Valchev
> Assignee: Valentin Valchev
> Fix For: webconsole-4.2.12
>
>
> The following exception occurs, when you try to save the webconsole
> configuration from the web console config plugin:
> {code}
> java.lang.NullPointerException
>
> java.security.MessageDigest$Delegate(java.security.MessageDigest).update(byte[])
> line: 293
>
> java.security.MessageDigest$Delegate(java.security.MessageDigest).digest(byte[])
> line: 368
>
> org.apache.felix.webconsole.internal.servlet.Password.hashPassword(byte[],
> java.lang.String) line: 178
>
> org.apache.felix.webconsole.internal.servlet.Password.hashPassword(java.lang.String,
> byte[]) line: 118
>
> org.apache.felix.webconsole.internal.servlet.Password.hashPassword(java.lang.String)
> line: 77
> {code}
> The implementation obviously expects password to be always set.
> However initially the configuration doesn't exist and when you create it with
> web console, the password is not set yet.
> However, if you do not edit the password in the configuration dialog, it is
> set to a PASSWORD_PLACEHOLDER_VALUE = "unmodifed".
> Then the following code becomes the reason of the problem, because of the
> incorrect assumption:
> {code}
> // assumption: config is not null and as a non-null password String property
> final String pwd = ( String ) config.get( OsgiManager.PROP_PASSWORD );
> final String hashedPassword = Password.hashPassword( pwd );
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FELIX-4995) NPE when updating Apache Felix OSGi Management Console configuration without a password
Valentin Valchev created FELIX-4995:
---
Summary: NPE when updating Apache Felix OSGi Management Console
configuration without a password
Key: FELIX-4995
URL: https://issues.apache.org/jira/browse/FELIX-4995
Project: Felix
Issue Type: Bug
Components: Web Console
Affects Versions: webconsole-4.2.8
Reporter: Valentin Valchev
The following exception occurs, when you try to save the webconsole
configuration from the web console config plugin:
{code}
java.lang.NullPointerException
java.security.MessageDigest$Delegate(java.security.MessageDigest).update(byte[])
line: 293
java.security.MessageDigest$Delegate(java.security.MessageDigest).digest(byte[])
line: 368
org.apache.felix.webconsole.internal.servlet.Password.hashPassword(byte[],
java.lang.String) line: 178
org.apache.felix.webconsole.internal.servlet.Password.hashPassword(java.lang.String,
byte[]) line: 118
org.apache.felix.webconsole.internal.servlet.Password.hashPassword(java.lang.String)
line: 77
{code}
The implementation obviously expects password to be always set.
However initially the configuration doesn't exist and when you create it with
web console, the password is not set yet.
However, if you do not edit the password in the configuration dialog, it is set
to a PASSWORD_PLACEHOLDER_VALUE = "unmodifed".
Then the following code becomes the reason of the problem, because of the
incorrect assumption:
{code}
// assumption: config is not null and as a non-null password String property
final String pwd = ( String ) config.get( OsgiManager.PROP_PASSWORD );
final String hashedPassword = Password.hashPassword( pwd );
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FELIX-4992) Webconsole config admin set fails with Lightweight HTTP
[ https://issues.apache.org/jira/browse/FELIX-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660136#comment-14660136 ] Valentin Valchev commented on FELIX-4992: - This is because most java http servers in their HttpServletResponse.sendRedirect() send the location header and set SC_FOUND status code (302)., while httplite sends SC_TEMPORARY_REDIRECT (307). > Webconsole config admin set fails with Lightweight HTTP > --- > > Key: FELIX-4992 > URL: https://issues.apache.org/jira/browse/FELIX-4992 > Project: Felix > Issue Type: Bug > Components: Lightweight HTTP Service, Web Console >Affects Versions: webconsole-4.2.10 > Environment: debian linux amd64 1.7 or 1.8 jvm firefox (debian > iceweasel) >Reporter: Ed Schaller > > Attempting to set or modify a configuration property results in the browser > repeatedly asking to allow a redirect. This happens repeatedly (10+ times) > until finaly an ajax error is presented. In the case of creating a new > configuration for a factory, the configuration is created with the default > values despite the loop but the values that were attempted to be set don't > get set. > httplite-0.1.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Felix Web Console Memory Usage Plugin 1.0.6
Hi Carsten,
Our test team discovered, that there is a slight problem, with this
release, when the framework is run in security mode. The bundle
implements ManagedServer but in it's updated method it performs
operation that requires special permission. Because the memoryusage
bundles doesn't use doPrivileged, the configuration admin bundle is also
in the stack trace. In that case, if the CM bundle doesn't have the
required permission, security exception will be thrown:
fw>$#0 DEBUG > [SecuritySimple] Insufficient local permissions:
bundle: com.prosyst.mbs.osgi.cm.bundle; permission:
("java.lang.management.ManagementPermission" "control"); local perms:
Bundle: ../../../bundles/com.prosyst.mbs.osgi.cm.bundle.jar
at
com.prosyst.mbs.impl.framework.module.security.PPermissions.implies(PPermissions.java:288)
at java.security.ProtectionDomain.implies(ProtectionDomain.java:276)
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:350)
at
com.prosyst.mbs.impl.framework.module.security.SecurityManagerImpl.checkPermission(SecurityManagerImpl.java:110)
at
com.prosyst.mbs.impl.framework.module.security.SecurityManagerImpl.checkPermission(SecurityManagerImpl.java:71)
at
com.prosyst.mbs.impl.framework.PSecurityManager.checkPermission(PSecurityManager.java:243)
at sun.management.Util.checkAccess(Util.java:77)
at sun.management.Util.checkControlAccess(Util.java:85)
at
sun.management.MemoryPoolImpl.setUsageThreshold(MemoryPoolImpl.java:118)
at
org.apache.felix.webconsole.plugins.memoryusage.internal.MemoryUsageSupport.setThreshold(MemoryUsageSupport.java:244)
at
org.apache.felix.webconsole.plugins.memoryusage.internal.MemoryUsageConfigurator.updated(MemoryUsageConfigurator.java:85)
Regards,
Valentin
On 24/04/2015 09:22, Carsten Ziegeler wrote:
> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/browse/FELIX-4862
>
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachefelix-1066/
>
> 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 1066 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Regards
> Carsten
--
-
Valentin Valchev · Lead Software Engineer
ProSyst Labs EOOD
1606 Sofia, Bulgaria · 48 Vladajska Str.
Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17
http://www.prosyst.com · v.valc...@prosyst.bg
-
stay in touch with your product.
-
[RESULT] [VOTE] Release webconsole-4.2.8, webconsole-useradmin-plugin-1.0.2 and webconsole-upnp-plugin-1.0.6
Hi, The vote has passed with the following result : +1 (binding): Carsten Ziegeler, Clement Escoffier, Pierre De Rop +1 (non binding): Jamie G, Jean-Baptiste Onofré I would ask a member of the Apache Felix PMC to promote the release and upload artifacts to maven central. (http://felix.apache.org/documentation/development/release-management-nexus.html#promoting-the-release) Meanwhile, I'll fix the versions in the JIRA project. Regards, Valentin Valchev On 14/03/2015 15:39, Carsten Ziegeler wrote: > Sorry, somehow I missed the vote mail :( > > Here's my +1 for the three releases. On 14/03/2015 15:51, clement escoffier wrote: > +1, On 14/03/2015 16:07, Pierre De Rop wrote: > +1 On 14/03/2015 21:10, Jamie G. wrote: > +1 (non-binding) On 14/03/2015 21:16, Jean-Baptiste Onofré wrote: > +1 (non binding) -- --------- Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - <> signature.asc Description: OpenPGP digital signature
Re: [VOTE] Release webconsole-4.2.8, webconsole-useradmin-plugin-1.0.2 and webconsole-upnp-plugin-1.0.6
There is no a single vote yet. Come on people. Regards, Valentin On 10/03/2015 15:30, Valentin Valchev wrote: > Hi all, > There are 3 new releases waiting for your approval: > > * webconsole-4.2.8 > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329340&styleName=Text&projectId=12310100 > > * webconsole-useradmin-plugin-1.0.2 > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329243&styleName=Text&projectId=12310100 > > * webconsole-upnp-plugin-1.0.6 > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329242&styleName=Text&projectId=12310100 > > > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-1057/ > > 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 1057 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > > Regards, > Valentin > -- - Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - <> signature.asc Description: OpenPGP digital signature
[VOTE] Release webconsole-4.2.8, webconsole-useradmin-plugin-1.0.2 and webconsole-upnp-plugin-1.0.6
Hi all, There are 3 new releases waiting for your approval: * webconsole-4.2.8 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329340&styleName=Text&projectId=12310100 * webconsole-useradmin-plugin-1.0.2 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329243&styleName=Text&projectId=12310100 * webconsole-upnp-plugin-1.0.6 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329242&styleName=Text&projectId=12310100 Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-1057/ 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 1057 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for at least 72 hours. Regards, Valentin -- --------- Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - <> signature.asc Description: OpenPGP digital signature
[jira] [Resolved] (FELIX-3633) User Admin Plugin - no German translation
[ https://issues.apache.org/jira/browse/FELIX-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-3633. - Resolution: Fixed Fix Version/s: webconsole-useradmin-plugin-1.0.2 Assignee: Valentin Valchev fixed in rev.1665428 > User Admin Plugin - no German translation > - > > Key: FELIX-3633 > URL: https://issues.apache.org/jira/browse/FELIX-3633 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-useradmin-plugin-1.0.0 > Reporter: Valentin Valchev > Assignee: Valentin Valchev > Fix For: webconsole-useradmin-plugin-1.0.2 > > Attachments: bundle_de.properties > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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 ] Valentin Valchev updated FELIX-3634: Fix Version/s: (was: webconsole-useradmin-plugin-1.0.2) > 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 > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-3633) User Admin Plugin - no German translation
[ https://issues.apache.org/jira/browse/FELIX-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev updated FELIX-3633: Fix Version/s: (was: webconsole-useradmin-plugin-1.0.2) > User Admin Plugin - no German translation > - > > Key: FELIX-3633 > URL: https://issues.apache.org/jira/browse/FELIX-3633 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-useradmin-plugin-1.0.0 > Reporter: Valentin Valchev > Attachments: bundle_de.properties > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-3695) When bundle filter doesn't match, the tool bars are duplicated
[ https://issues.apache.org/jira/browse/FELIX-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-3695. - Resolution: Fixed Fix Version/s: webconsole-4.2.8 Assignee: Valentin Valchev Fixed as suggested by Felix in rev. 1665413 > When bundle filter doesn't match, the tool bars are duplicated > -- > > Key: FELIX-3695 > URL: https://issues.apache.org/jira/browse/FELIX-3695 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Evgeni Grigorov >Assignee: Valentin Valchev >Priority: Minor > Fix For: webconsole-4.2.8 > > Attachments: duplicated_toolbars.jpg > > > The issue can be reproduced with the help of: > - open Bundles tab > - go to the filter field > - type a filter, which doesn't match - for example "aa" > As a result, no bundles are visualized and the tool bars are duplicated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14354511#comment-14354511 ] Valentin Valchev commented on FELIX-3878: - Well, actually the web console uses the standard OSGi localization mechanism and that is to use the Bundle-Localization header, that points to a properties resource bundle. By default, the localization is not metatype.properties but OSGI-INF/l10n/bundle.properties To localize the bundle name/description you should set it's manifest like: Bundle-Name: %bundle.name and have the following property in the resource bundle: bundle.name=My Localized Bundle name The above mechanism already works in the Web Console in the Bundles plugin. You just need to install one of the locale bundles and select the required locale. If available, the name of the bundle will be shown as expected. I'm not sure though, that we support localization of service.description registration property. Am I missing something from the OSGi spec? > 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 (v6.3.4#6332)
[jira] [Resolved] (FELIX-2464) Web Console Events plugin XML encoding
[ https://issues.apache.org/jira/browse/FELIX-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-2464. - Resolution: Invalid You are right. I'm closing the issue. > Web Console Events plugin XML encoding > -- > > Key: FELIX-2464 > URL: https://issues.apache.org/jira/browse/FELIX-2464 > Project: Felix > Issue Type: Task > Components: Web Console >Affects Versions: webconsole-event-plugin-1.0.2 > Reporter: Valentin Valchev >Priority: Trivial > > The file > webconsole-plugins\event\src\main\resources\OSGI-INF\metatype\metatype.xml is > encoded in UTF without BOM. Is there any special reason for omitting the BOM? > Without BOM, some XML parsers (typically older versions) might not correctly > detect the character set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[DISCUSS] Releasing web console with few other plugins
Hello, I would like to release the following web console plugins and the web console itself: - webconsole-upnp-plugin-1.0.6 (with one blocker issue fixed) - webconsole-4.2.8 (1 major issue and finally logout button) - webconsole-ds-plugin-1.0.2 (improvements and synchronization with latest web console - appear as item in OSGi menu) - webconsole-useradmin-plugin-1.0.2 (one minor usability issue) Any objections or pending issues to include ? Here is more detailed changelog: Release Notes - Felix - Version webconsole-upnp-plugin-1.0.6 ** Bug * [FELIX-4747] - Executing actions with parameters on UPnP devices does not work Release Notes - Felix - Version webconsole-4.2.8 ** Bug * [FELIX-4800] - Bundle search in /system/console/bundles produces 405 ** Improvement * [FELIX-3006] - Please create a logout button for the web console screen Release Notes - Felix - Version webconsole-ds-plugin-1.0.2 ** Bug * [FELIX-4559] - DS plugin should use Inventory instead of deprecated ConfigurationPrinter ** Improvement * [FELIX-3140] - Display link for component id within the bundle details and service details view * [FELIX-3861] - Set felix.webconsole.category on Web Console plugins * [FELIX-4786] - Update to latest DS implementation Release Notes - Felix - Version webconsole-useradmin-plugin-1.0.2 ** Bug * [FELIX-4763] - Reload button on user admin plugin doesn't work correctly. Regards, Valentin Valchev -- - Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - <> signature.asc Description: OpenPGP digital signature
[jira] [Resolved] (FELIX-4747) Executing actions with parameters on UPnP devices does not work
[ https://issues.apache.org/jira/browse/FELIX-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-4747. - Resolution: Fixed fixed in SVN rev. 1649521 from 05/01/2015 > Executing actions with parameters on UPnP devices does not work > --- > > Key: FELIX-4747 > URL: https://issues.apache.org/jira/browse/FELIX-4747 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-upnp-plugin-1.0.4 > Reporter: Valentin Valchev > Assignee: Valentin Valchev >Priority: Blocker > Fix For: webconsole-upnp-plugin-1.0.6 > > > There is a problem with serialization/deserialization of the the action > parameters in UPnP Web Console plugin. > In the javascript code the action invocation is serialized as JSON object, > containing 'names' and 'vals', which are arrays of strings. > However, on the Java side, the keys are read as 'names[]' and 'vals[]'. > Probably, that's due to changes in jquery or it's a bug, since the plugin is > created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-3006) Please create a logout button for the web console screen
[ https://issues.apache.org/jira/browse/FELIX-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339851#comment-14339851 ] Valentin Valchev commented on FELIX-3006: - [~cziegeler] I've checked out the code, tested it, it works. So I would say - it's perfect! ;) > Please create a logout button for the web console screen > > > Key: FELIX-3006 > URL: https://issues.apache.org/jira/browse/FELIX-3006 > Project: Felix > Issue Type: Improvement > Components: Web Console >Reporter: Susan Javurek >Assignee: Carsten Ziegeler > Fix For: webconsole-4.2.8 > > Attachments: FELIX-3006.diff, logout.diff, logout2.diff > > > Please add a log out button on the web console to avoid sessions and cookies > being retained. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-3006) Please create a logout button for the web console screen
[ https://issues.apache.org/jira/browse/FELIX-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev updated FELIX-3006: Attachment: logout2.diff Update the patch. The new one does the following things in addition: 1. doesn't invalidate the session. This will create problems if the session is implemented as cookies and the session attribute will be lost 2. use request.sendError instead of request.setStatus. Otherwise some browsers wait a lot before the login dialog appears. Here is example situation for #1: session is invalidated & cookie is removed. Then new session is created and the attribute is set. However the browser doesn't set the cookie, because WWW-Authenticate is set. The next time when you open webconsole, a new session will be created because of missing cookie. That way the the session attribute is lost. > Please create a logout button for the web console screen > > > Key: FELIX-3006 > URL: https://issues.apache.org/jira/browse/FELIX-3006 > Project: Felix > Issue Type: Improvement > Components: Web Console >Reporter: Susan Javurek > Attachments: FELIX-3006.diff, logout.diff, logout2.diff > > > Please add a log out button on the web console to avoid sessions and cookies > being retained. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-3006) Please create a logout button for the web console screen
[ https://issues.apache.org/jira/browse/FELIX-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328657#comment-14328657 ] Valentin Valchev commented on FELIX-3006: - When you open /system/console/logout here what happens: 1. webconsole performs logout and request the browser to authenticate 2. the browser opens username/password dialog and asks the user to enter his credentials 3. then the browser sends a new request with basic authentication included to /system/console/logout 4.the the web console performs logout (step #1).. and this is an endless cycle In order to prevent the endless cycle, in step #4, the webconsole will redirect the user to the default plugin. To differentiate between step #1 and step #4, I use a session attribute. It is not available in step #1 and available in step #4. I couldn't figure it out how to fix the issue above, without a session. > Please create a logout button for the web console screen > > > Key: FELIX-3006 > URL: https://issues.apache.org/jira/browse/FELIX-3006 > Project: Felix > Issue Type: Improvement > Components: Web Console >Reporter: Susan Javurek > Attachments: FELIX-3006.diff, logout.diff > > > Please add a log out button on the web console to avoid sessions and cookies > being retained. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-3006) Please create a logout button for the web console screen
[ https://issues.apache.org/jira/browse/FELIX-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev updated FELIX-3006: Attachment: logout.diff Attached logout.diff Here are the changes in brief: - added new WebConsoleSecurityProvider3 that has logout() method. The reason for that is, if the user provides a login() mechanism, they know better how to logout. So if this provider is available, it is completely responsible for performing the logout. - as fail-back if the default basic authentication is used, the webconsole will send again WWW-Authenticate header, so the user has to enter it's credentials once again. - the logout procedure will also remove some OSGi & Web Console attributes, used to identity the current user - it will also prevent the user from looping over and over to the logout url - a new logout button integrates with the top menu bar (the categories) [~fmeschbe], [~cziegeler], please, can you review the patch so we can finally close that issue after 4 years ;) > Please create a logout button for the web console screen > > > Key: FELIX-3006 > URL: https://issues.apache.org/jira/browse/FELIX-3006 > Project: Felix > Issue Type: Improvement > Components: Web Console >Reporter: Susan Javurek > Attachments: FELIX-3006.diff, logout.diff > > > Please add a log out button on the web console to avoid sessions and cookies > being retained. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4767) Bulgarian i18n for Web Console is out of sync
[ https://issues.apache.org/jira/browse/FELIX-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-4767. - Resolution: Fixed fixed in svn rev.1653209 > Bulgarian i18n for Web Console is out of sync > - > > Key: FELIX-4767 > URL: https://issues.apache.org/jira/browse/FELIX-4767 > Project: Felix > Issue Type: Bug > Components: Web Console > Reporter: Valentin Valchev > Assignee: Valentin Valchev >Priority: Trivial > > The i18n bundle is out of sync. Some localization keys are missing and the > pom file doesn't correctly translate the properties with native2ascii. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4767) Bulgarian i18n for Web Console is out of sync
Valentin Valchev created FELIX-4767: --- Summary: Bulgarian i18n for Web Console is out of sync Key: FELIX-4767 URL: https://issues.apache.org/jira/browse/FELIX-4767 Project: Felix Issue Type: Bug Components: Web Console Reporter: Valentin Valchev Assignee: Valentin Valchev Priority: Trivial The i18n bundle is out of sync. Some localization keys are missing and the pom file doesn't correctly translate the properties with native2ascii. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: New Web Console Release?
Hello Carsten, There is one patch waiting for review that wasn't merged (https://issues.apache.org/jira/browse/FELIX-4734). Despite that, I have nothing to add. Regards, Valentin On 17/01/2015 12:15, Carsten Ziegeler wrote: > Hi, > > I'm planning to cut a new release of the web console mid next week, > especially to get a fix for FELIX-4735. > > Anything that needs to be done before? > > Thanks > Carsten -- ----- Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - <> signature.asc Description: OpenPGP digital signature
[jira] [Resolved] (FELIX-4763) Reload button on user admin plugin doesn't work correctly.
[ https://issues.apache.org/jira/browse/FELIX-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-4763. - Resolution: Fixed Fixed in SVN rev. 1651300 > Reload button on user admin plugin doesn't work correctly. > -- > > Key: FELIX-4763 > URL: https://issues.apache.org/jira/browse/FELIX-4763 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-useradmin-plugin-1.0.0 > Reporter: Valentin Valchev >Assignee: Valentin Valchev >Priority: Minor > Fix For: webconsole-useradmin-plugin-1.0.2 > > > The reload button works every even time, but every odd time you press the > button it doesn't do anything. > IMHO this could be a problem of the used tree library, which is pretty old. > It's probably best to upgrade to the latest version of jsTree. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4763) Reload button on user admin plugin doesn't work correctly.
Valentin Valchev created FELIX-4763: --- Summary: Reload button on user admin plugin doesn't work correctly. Key: FELIX-4763 URL: https://issues.apache.org/jira/browse/FELIX-4763 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-useradmin-plugin-1.0.0 Reporter: Valentin Valchev Assignee: Valentin Valchev Priority: Minor Fix For: webconsole-useradmin-plugin-1.0.2 The reload button works every even time, but every odd time you press the button it doesn't do anything. IMHO this could be a problem of the used tree library, which is pretty old. It's probably best to upgrade to the latest version of jsTree. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4747) Executing actions with parameters on UPnP devices does not work
Valentin Valchev created FELIX-4747: --- Summary: Executing actions with parameters on UPnP devices does not work Key: FELIX-4747 URL: https://issues.apache.org/jira/browse/FELIX-4747 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-upnp-plugin-1.0.4 Reporter: Valentin Valchev Assignee: Valentin Valchev Priority: Blocker Fix For: webconsole-upnp-plugin-1.0.6 There is a problem with serialization/deserialization of the the action parameters in UPnP Web Console plugin. In the javascript code the action invocation is serialized as JSON object, containing 'names' and 'vals', which are arrays of strings. However, on the Java side, the keys are read as 'names[]' and 'vals[]'. Probably, that's due to changes in jquery or it's a bug, since the plugin is created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[VOTE RESULTS] Release Apache Felix Web Console UPnP Plugin 1.0.4
The vote passes with three binding +1 votes. Thank you all. Now I had to publish the staging repository. But I'm not a PMC member, so I would kindly ask you if somebody can publish the new release? Regards, Valentin On 16/12/2014 18:21, Clement Escoffier wrote: > +1, > > Regards, > > Clement On 19/12/2014 12:55, Carsten Ziegeler wrote: > +1 > > Carsten On 05/01/2015 10:27, David Bosschaert wrote: > +1 -- --------- Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - <> signature.asc Description: OpenPGP digital signature
[VOTE RESULTS] Release Apache Felix Web Console Event Plugin 1.1.2
The vote passes with four binding +1 votes and one non-binding +1 vote. Thank you all. Now I had to publish the staging repository. But I'm not a PMC member, so I would kindly ask you if somebody can publish the new release? Regards, Valentin On 16/12/2014 18:20, Clement Escoffier wrote: > +1, > > Regards, > > Clement On 19/12/2014 12:54, Carsten Ziegeler wrote: > +1 > > Carsten On 21/12/2014 00:46, Pierre De Rop wrote: > +1 > > regards > /Pierre On 05/01/2015 10:31, David Bosschaert wrote: > +1 On 21/12/2014 06:56, Jean-Baptiste Onofré wrote: > +1 (non binding) > > Regards > JB -- --------- Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - <> signature.asc Description: OpenPGP digital signature
[VOTE RESULTS] Release Apache Felix Web Console User Admin Plugin 1.0.0
The vote passes with three binding +1 votes. Thank you all. Now I had to publish the staging repository. But I'm not a PMC member, so I would kindly ask you if somebody can publish the new release? Regards, Valentin On 16/12/2014 18:21, Clement Escoffier wrote: > +1, > > Regards, > > Clement On 19/12/2014 12:55, Carsten Ziegeler wrote: > +1 > > Carsten On 05/01/2015 10:27, David Bosschaert wrote: > +1 -- --------- Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - <> signature.asc Description: OpenPGP digital signature
[jira] [Commented] (FELIX-3773) WebConsole uses library with ASL-incompatible licence
[ https://issues.apache.org/jira/browse/FELIX-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264380#comment-14264380 ] Valentin Valchev commented on FELIX-3773: - [~cziegeler] IMHO - this change should get in webconsole 5.0 because it might break some API compatibility and will definitely break some deployment configurations. > 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 (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14253471#comment-14253471
]
Valentin Valchev commented on FELIX-4734:
-
FELIX-600 is somehow related to this issue
> 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
> 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] [Updated] (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
]
Valentin Valchev updated FELIX-4734:
Attachment: FELIX-4734.patch
I'm attaching a patch that:
- removes all unnecessary waits
- always waits for refresh package to complete
-- at most 5 seconds for a single bundle packages refresh
-- at most 15 seconds for the whole framework packages refresh
- it doesn't uses the wiring, since I'm trying to keep webconsole OSGi 4.0
compliant
I didn't make update to do refresh packages. Considering that web console is
developer tool, for me it's better to update the bundle(s) I need, and then to
refresh the packages.
Looking forward for your review.
> 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
> 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] [Commented] (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:comment-tabpanel&focusedCommentId=14253147#comment-14253147
]
Valentin Valchev commented on FELIX-4734:
-
IMHO the web console shouldn't way at all, but you might be right, that it's
more convenient that way.
Looking at the code, I think that web console waits all the time, but that
completely unnecessary for install, start, stop..
But for sure - we should wait for refresh(bundle) and refreshPackages and
probably update(bundle). And blind waiting is really not enough. So I'll think
about it and propose a patch.
> 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
>
> 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] [Updated] (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 ] Valentin Valchev updated FELIX-4735: Affects Version/s: webconsole-4.2.4 > 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] [Resolved] (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 ] Valentin Valchev resolved FELIX-4735. - Resolution: Fixed fixed in svn rev. 1646649 > 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] [Created] (FELIX-4735) Cannot create a new factory configuration from Web Admin Console
Valentin Valchev created FELIX-4735: --- Summary: 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 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)
Re: [VOTE] Release Apache Felix Web Console Event Plugin 1.1.2
Hello Clement, Right, I didn't modified the file, but I was pointed to this FAQ: http://people.apache.org/~henkp/checker/faq.html#3 "please note that KEYS files are deprecated in that they could/should be generated from the info maintained in id.apache.org <https://id.apache.org/>." So I'm not sure if I should manually update the file or wait for some scheduled operation? Regards, Valentin On 16/12/2014 16:28, Clement Escoffier wrote: > Hi, > > I can’t find your PGP public key in http://www.apache.org/dist/felix/KEYS. > Could you update it, so we can check your release. > You can check the Appendix A of > http://felix.apache.org/documentation/development/release-management-nexus.html > to get the upload instruction. > > Cheers, > > Clement > On 16 décembre 2014 at 13:43:00, Valentin Valchev (v.valc...@prosyst.bg) > wrote: > > Call for a vote on Apache Felix Web Console Event Plugin 1.1.2 > > Staging repository available at > > https://repository.apache.org/content/groups/staging/org/apache/felix/org.apache.felix.webconsole.plugins.event/1.1.2/ > > > Release Notes - Felix - Version webconsole-event-plugin-1.1.2 > > --- > > ** Bug > * [FELIX-4573] - Web Console Event plugin might cease operation if Event > property is null > * [FELIX-4731] - Event plugin native2ascii plugin conflicts with Eclipse > * [FELIX-4732] - Web Console event plugin is not compatible with OSGi/Minimum > EE > > ** New Feature > * [FELIX-4499] - BundleEventConverter reports UNINSTALLED for UNRESOLVED > events > * [FELIX-4500] - EventListener should implement SynchronousBundleListener > > > 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 1046 /tmp/felix-staging > > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > This vote will be open for 72 hours. > > > Best regards, > Valentin Valchev > > -- > > - > Valentin Valchev · Lead Software Engineer > ProSyst Labs EOOD > 1606 Sofia, Bulgaria · 48 Vladajska Str. > Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 > http://www.prosyst.com · v.valc...@prosyst.bg > - > stay in touch with your product. > - > > -- - Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - <> signature.asc Description: OpenPGP digital signature
[VOTE] Release Apache Felix Web Console Event Plugin 1.1.2
Call for a vote on Apache Felix Web Console Event Plugin 1.1.2 Staging repository available at https://repository.apache.org/content/groups/staging/org/apache/felix/org.apache.felix.webconsole.plugins.event/1.1.2/ Release Notes - Felix - Version webconsole-event-plugin-1.1.2 --- ** Bug * [FELIX-4573] - Web Console Event plugin might cease operation if Event property is null * [FELIX-4731] - Event plugin native2ascii plugin conflicts with Eclipse * [FELIX-4732] - Web Console event plugin is not compatible with OSGi/Minimum EE ** New Feature * [FELIX-4499] - BundleEventConverter reports UNINSTALLED for UNRESOLVED events * [FELIX-4500] - EventListener should implement SynchronousBundleListener 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 1046 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours. Best regards, Valentin Valchev -- - Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - <> signature.asc Description: OpenPGP digital signature
[VOTE] Release Apache Felix Web Console User Admin Plugin 1.0.0
Call for a vote on Apache Felix Web Console User Admin Plugin 1.0.0 Staging repository available at https://repository.apache.org/content/groups/staging/org/apache/felix/org.apache.felix.webconsole.plugins.useradmin/1.0.0/ Release Notes - Felix - Version webconsole-useradmin-plugin-1.0.0 --- ** Bug * [FELIX-3633] - User Admin Plugin - no German translation * [FELIX-3634] - User Admin Plugin - no Russian translation ** Improvement * [FELIX-2254] - User Admin Plugin * [FELIX-3861] - Set felix.webconsole.category on Web Console plugins * [FELIX-4703] - User Admin plugin should use all available to the JVM crypto algorithms 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 1046 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours. Best regards, Valentin Valchev -- - Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - signature.asc Description: OpenPGP digital signature
[VOTE] Release Apache Felix Web Console UPnP Plugin 1.0.4
Call for a vote on Apache Felix Web Console UPnP Plugin 1.0.4 Staging repository available at https://repository.apache.org/content/groups/staging/org/apache/felix/org.apache.felix.webconsole.plugins.upnp/1.0.4/ Release Notes - Felix - Version webconsole-upnp-plugin-1.0.4 --- ** Bug * [FELIX-3589] - The service id link for UPnP devices doesn't work * [FELIX-3595] - NPE in ControlServlet.addingService * [FELIX-3669] - NPE in ControlServlet.deviceToJSON * [FELIX-4012] - Sometimes the UPnP plugin fails to start due to device being removed from network * [FELIX-4013] - Incorrect usage of ServiceTracker.size() in UPnP Plugin * [FELIX-4032] - UPnP Plugin small refactoring * [FELIX-4560] - Unsynchonized access to map can cause infinite loop in UPnP web console plugin * [FELIX-4733] - UPnP plugin native2ascii plugin conflicts with Eclipse m2e ** Improvement * [FELIX-3861] - Set felix.webconsole.category on Web Console plugins * [FELIX-4016] - Provide more meta data to the UPnP action arguments 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 1046 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours. Best regards, Valentin Valchev -- - Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - signature.asc Description: OpenPGP digital signature
[jira] [Resolved] (FELIX-4733) UPnP plugin native2ascii plugin conflicts with Eclipse m2e
[ https://issues.apache.org/jira/browse/FELIX-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-4733. - Resolution: Fixed Fixed in rev 1645889 > UPnP plugin native2ascii plugin conflicts with Eclipse m2e > -- > > Key: FELIX-4733 > URL: https://issues.apache.org/jira/browse/FELIX-4733 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-upnp-plugin-1.0.2 > Reporter: Valentin Valchev > Assignee: Valentin Valchev >Priority: Critical > Fix For: webconsole-upnp-plugin-1.0.4 > > > There was similar issue with the event admin plugin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4733) UPnP plugin native2ascii plugin conflicts with Eclipse m2e
Valentin Valchev created FELIX-4733: --- Summary: UPnP plugin native2ascii plugin conflicts with Eclipse m2e Key: FELIX-4733 URL: https://issues.apache.org/jira/browse/FELIX-4733 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-upnp-plugin-1.0.2 Reporter: Valentin Valchev Assignee: Valentin Valchev Priority: Critical Fix For: webconsole-upnp-plugin-1.0.4 There was similar issue with the event admin plugin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4732) Web Console event plugin is not compatible with OSGi/Minimum EE
[ https://issues.apache.org/jira/browse/FELIX-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev resolved FELIX-4732. - Resolution: Fixed Fixed in rev.1645886 > Web Console event plugin is not compatible with OSGi/Minimum EE > --- > > Key: FELIX-4732 > URL: https://issues.apache.org/jira/browse/FELIX-4732 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-event-plugin-1.1.0 > Reporter: Valentin Valchev > Assignee: Valentin Valchev > Fix For: webconsole-event-plugin-1.1.2 > > > Character.valueOf() is not available in OSGi/Minimum Execution Environment. > That prevents the plugin from running on embedded JVMs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4731) Event plugin native2ascii plugin conflicts with Eclipse
[
https://issues.apache.org/jira/browse/FELIX-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Valchev resolved FELIX-4731.
-
Resolution: Fixed
Fixed in rev.1645885
> Event plugin native2ascii plugin conflicts with Eclipse
> ---
>
> Key: FELIX-4731
> URL: https://issues.apache.org/jira/browse/FELIX-4731
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-event-plugin-1.1.0
> Reporter: Valentin Valchev
> Assignee: Valentin Valchev
>Priority: Critical
> Fix For: webconsole-event-plugin-1.1.2
>
>
> When the event plugin is imported in Eclipse as "Existing Maven Project" the
> project is not correctly generated because of the following section:
> {code}
>
> target/classes
>
> OSGI-INF/**
>
> false
>
> {code}
> If you uncomment it, then resources processed by native2ascii doesn't get
> included.
> I've found a solution, and it is to remove the additional resources, but
> instead add the following instruction to the maven-bundle-plugin:
> {code}
> {maven-resources},OSGI-INF=target/classes/OSGI-INF
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FELIX-4732) Web Console event plugin is not compatible with OSGi/Minimum EE
Valentin Valchev created FELIX-4732: --- Summary: Web Console event plugin is not compatible with OSGi/Minimum EE Key: FELIX-4732 URL: https://issues.apache.org/jira/browse/FELIX-4732 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-event-plugin-1.1.0 Reporter: Valentin Valchev Assignee: Valentin Valchev Fix For: webconsole-event-plugin-1.1.2 Character.valueOf() is not available in OSGi/Minimum Execution Environment. That prevents the plugin from running on embedded JVMs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4731) Event plugin native2ascii plugin conflicts with Eclipse
[
https://issues.apache.org/jira/browse/FELIX-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Valchev updated FELIX-4731:
Affects Version/s: webconsole-event-plugin-1.1.0
> Event plugin native2ascii plugin conflicts with Eclipse
> ---
>
> Key: FELIX-4731
> URL: https://issues.apache.org/jira/browse/FELIX-4731
> Project: Felix
> Issue Type: Bug
> Components: Web Console
>Affects Versions: webconsole-event-plugin-1.1.0
> Reporter: Valentin Valchev
> Assignee: Valentin Valchev
>Priority: Critical
> Fix For: webconsole-event-plugin-1.1.2
>
>
> When the event plugin is imported in Eclipse as "Existing Maven Project" the
> project is not correctly generated because of the following section:
> {code}
>
> target/classes
>
> OSGI-INF/**
>
> false
>
> {code}
> If you uncomment it, then resources processed by native2ascii doesn't get
> included.
> I've found a solution, and it is to remove the additional resources, but
> instead add the following instruction to the maven-bundle-plugin:
> {code}
> {maven-resources},OSGI-INF=target/classes/OSGI-INF
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FELIX-4731) Event plugin native2ascii plugin conflicts with Eclipse
Valentin Valchev created FELIX-4731:
---
Summary: Event plugin native2ascii plugin conflicts with Eclipse
Key: FELIX-4731
URL: https://issues.apache.org/jira/browse/FELIX-4731
Project: Felix
Issue Type: Bug
Components: Web Console
Reporter: Valentin Valchev
Assignee: Valentin Valchev
Priority: Critical
Fix For: webconsole-event-plugin-1.1.2
When the event plugin is imported in Eclipse as "Existing Maven Project" the
project is not correctly generated because of the following section:
{code}
target/classes
OSGI-INF/**
false
{code}
If you uncomment it, then resources processed by native2ascii doesn't get
included.
I've found a solution, and it is to remove the additional resources, but
instead add the following instruction to the maven-bundle-plugin:
{code}
{maven-resources},OSGI-INF=target/classes/OSGI-INF
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[VOTE RESULT] Release Apache Felix Web Console 4.2.4
The vote passes with four binding +1 votes. Thank you all. Now I had to publish the staging repository. But I'm not a PMC member, so I would kindly ask you if somebody can publish the new release? Regards, Valentin > On 10/12/2014 16:35, David Bosschaert wrote: > +1 > > David > > On 10 December 2014 at 14:26, Clement Escoffier > wrote: > +1, > > Regards, > > Clement > > On 10 décembre 2014 at 14:58:11, Carsten Ziegeler (cziege...@apache.org) wrote: > > +1 > > Carsten > On 11/12/2014 22:41, Pierre De Rop wrote: > Hi Valentin; > > +1 > > regards; > /Pierre -- - Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - <> signature.asc Description: OpenPGP digital signature
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14242261#comment-14242261 ] Valentin Valchev commented on FELIX-4720: - I looked at Log Service TCK and completely agree that Equinox Log service will pass it. Anyway, to help your implementation, here are some problems that we've met before: 1. You have a bundle with native code - there is an exception class declared in that bundle - the exception is thrown somewhere and logged - if the log entry, with the exception above is inside the log queue, the bundle update will fail * the reason is that the class loader of the first version of the bundle cannot be discarded, so the native library is not unloaded. When the new version is installed, and tries to load the native library it will fails, because the library is already loaded. ! the solution is to use the method mentioned by LogReaderService.getLog() - to wrap the exception so you don't keep references to the original exception 2. If you are using IBM J9/VAME virtual machine : - you may throw and log IOException as example - in that case your bundle becomes part of the stack trace - your bundle is updated or uninstalled - another bundle uses the log reader to get the exceptions - when that bundle gets the IOException and tries to print the stack trace the virtual machine dies ! the solution is same as above -- At ProSyst we using Web Console a lot and we also invest a lot of it's development and improvements. We also contributed few other plugins that covers core OSGi functionality like user admin and upnp plugin. We've already invested hundreds of man-hours on development and testing. I convinced my boss that Apache Web Console is good and quality product, that's why we invested so much in it. I personally will not be happy, if Web Console is the cause of JVM crashes and be blamed for that. > 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 > > 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 (v6.3.4#6332)
Re: [VOTE] Release Apache Felix Web Console 4.2.4
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 1045 /tmp/felix-staging (Just copy-paste from other votes, fixed the number. Though how do you get that number? I opened the repository and saw it's there. So I'm just guessing it's the correct one.) On 10/12/2014 12:18, Carsten Ziegeler wrote: > How can we use the check script to verify this release? > > Regards > Carsten > > Am 09.12.14 um 16:16 schrieb Valentin Valchev: >> Call for a vote on Apache Felix Web Console 4.2.4 >> >> Staging repository available at >> >> https://repository.apache.org/content/groups/staging/org/apache/felix/org.apache.felix.webconsole/4.2.4/ >> >> Release Notes - Felix - Version webconsole-4.2.4 >> >> ** Bug >> * [FELIX-3817] - Form parameters might clash with configuration >> parameters >> * [FELIX-4558] - Web Console Service plugin doesn't list properties >> with value 0 >> * [FELIX-4562] - Web Console License plugin fails to load files >> * [FELIX-4572] - Web Console may cause NPE on refresh packages >> * [FELIX-4610] - WebConsole doesn't start with Java Security enabled >> * [FELIX-4652] - Security problem with >> AbstractWebConsolePlugin.spoolResource >> * [FELIX-4660] - Security problem in WebConsoleUtil.getParameter() >> method >> * [FELIX-4662] - WebConsole Xdialog javascript function is not >> working correctly >> >> ** Improvement >> * [FELIX-3848] - Differentiate between unbound and new configuration >> * [FELIX-4711] - Web Console: False AJAX error displayed on deleting >> or unbinding config >> >> >> Please review and vote ! >> >> Best regards, >> Valentin Valchev >> > -- - Valentin Valchev · Lead Software Engineer ProSyst Labs EOOD 1606 Sofia, Bulgaria · 48 Vladajska Str. Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17 http://www.prosyst.com · v.valc...@prosyst.bg - stay in touch with your product. - <> signature.asc Description: OpenPGP digital signature
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14240842#comment-14240842 ] Valentin Valchev commented on FELIX-4720: - The problem here is not only if we should do it or not. There are two much more significant problems: 1. As a consultant, when I go to a client and want to convince them that OSGi is great, one of the key benefits I point to is that it is standard, and they have the freedom to choose whatever implementation they want and it still will work in compatible way. OSGi has a TCK that verifies the implementations and certifies them for compatibility. 2. The other thing is *usability*. As a developer I can just implement own log queue and it will go great. But as product manager I should also care of *how clients feel it* - and it should be *easy and intuitive*. If they had to configure 2+ log queues, that's not acceptable for them, then also not for me. > 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 > > 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 (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14239551#comment-14239551
]
Valentin Valchev commented on FELIX-4720:
-
Imagine that you go to the grocery store. Then you have to pay:
- the tomatoes on cashier #1
- cucumbers on cashier #2
- all fruits on cashier #3
Would you visit that grocery store twice?
That's the same with the log storage. If I'm system integrator and had to
configure
- log queue of the log service
- log queue of the web console
- log queue of the gogo shell
he/she will be you, in the grocery store. Not use it again!
If I'm developer and create a queue
- i could be blamed if the queue is not configurable
- i could be blamed if there are bugs in the queue
- i could be blamed if it keeps some references to other bundles (through stack
trace elements of the exceptions)
But I have a *standard*, that says - there is a log queue. You bet, I'll use
it, instead of duplicating it.
Carsten, you said, that we can create a common queue, that is independent of
log reader. So, if not using equinox implementation, you will buffer the
entries twice and use more memory than needed?
And what about code reuse? - one the best features of OSGi is that you can
share the code, and use import-export, instead of copy-paste.
What about reliability and compliance? Can I trust the OSGi standard if we need
to change applications, because some vendor doesn't implement it fully?
P.S: I'm posting some parts of org.osgi.service.log.LogEntry javadoc;
{code}
/**
* Returns the exception object associated with this {@code LogEntry}
* object.
*
*
* In some implementations, the returned exception may not be the
original
* exception. To avoid references to a bundle defined exception class,
thus
* preventing an uninstalled bundle from being garbage collected, the
Log
* Service may return an exception object of an implementation defined
* Throwable subclass. The returned object will attempt to provide as
much
* information as possible from the original exception object such as
the
* message and stack trace.
{code}
So, there *is* a way, to prevent pinning objects in memory when implementing
the log reader service. Is equinox, that decided not to implement it that way
and instead to return empty list of log entries. Although that the above
solution is simple, I agree, that it's slower and requires more temporary
memory. So it's inefficient. But if we want to correctly implement web console
log plugin, gogo shell log command, that inefficient code is multiplied by 2.
Or by 5, or 6 - depending how many applications do you have to browse the log
entries. And yet, if could be only 1 place - the LogReaderService.
> 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
>
> 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
(v6.3.4#6332)
[VOTE] Release Apache Felix Web Console 4.2.4
Call for a vote on Apache Felix Web Console 4.2.4 Staging repository available at https://repository.apache.org/content/groups/staging/org/apache/felix/org.apache.felix.webconsole/4.2.4/ Release Notes - Felix - Version webconsole-4.2.4 ** Bug * [FELIX-3817] - Form parameters might clash with configuration parameters * [FELIX-4558] - Web Console Service plugin doesn't list properties with value 0 * [FELIX-4562] - Web Console License plugin fails to load files * [FELIX-4572] - Web Console may cause NPE on refresh packages * [FELIX-4610] - WebConsole doesn't start with Java Security enabled * [FELIX-4652] - Security problem with AbstractWebConsolePlugin.spoolResource * [FELIX-4660] - Security problem in WebConsoleUtil.getParameter() method * [FELIX-4662] - WebConsole Xdialog javascript function is not working correctly ** Improvement * [FELIX-3848] - Differentiate between unbound and new configuration * [FELIX-4711] - Web Console: False AJAX error displayed on deleting or unbinding config Please review and vote ! Best regards, Valentin Valchev
[jira] [Updated] (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 ] Valentin Valchev updated FELIX-3614: Fix Version/s: (was: webconsole-4.2.4) Defering open issues to the future release > 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 > 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 (v6.3.4#6332)
[jira] [Updated] (FELIX-3760) Clean webconsole startup and disposal
[ https://issues.apache.org/jira/browse/FELIX-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Valchev updated FELIX-3760: Fix Version/s: (was: webconsole-4.2.4) Defering open issues to the future release > Clean webconsole startup and disposal > - > > Key: FELIX-3760 > URL: https://issues.apache.org/jira/browse/FELIX-3760 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > > The webconsole do hold locks while calling the OSGi framework which can cause > issues. > It also calls reconfigure itself at startup because the update(null) is > always called and the ConfigurationAdmin call it again with the correct > configuration just after the service registration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
