[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)
[jira] [Commented] (FELIX-4726) [Core R6] Update bundle and service hooks for the system bundle
[ https://issues.apache.org/jira/browse/FELIX-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242252#comment-14242252 ] David Bosschaert commented on FELIX-4726: - Changes for service hooks are done in http://svn.apache.org/viewvc?view=revision&revision=1644564 > [Core R6] Update bundle and service hooks for the system bundle > --- > > Key: FELIX-4726 > URL: https://issues.apache.org/jira/browse/FELIX-4726 > Project: Felix > Issue Type: Sub-task > Components: Framework >Reporter: David Bosschaert >Assignee: David Bosschaert > Fix For: framework-4.6.0 > > > The Core R6 spec has updates around Bundle and Service Hook behaviour in > relation to the system bundle. The Felix framework needs to be updated for > this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (FELIX-4726) [Core R6] Update bundle and service hooks for the system bundle
[ https://issues.apache.org/jira/browse/FELIX-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-4726 started by David Bosschaert. --- > [Core R6] Update bundle and service hooks for the system bundle > --- > > Key: FELIX-4726 > URL: https://issues.apache.org/jira/browse/FELIX-4726 > Project: Felix > Issue Type: Sub-task > Components: Framework >Reporter: David Bosschaert >Assignee: David Bosschaert > Fix For: framework-4.6.0 > > > The Core R6 spec has updates around Bundle and Service Hook behaviour in > relation to the system bundle. The Felix framework needs to be updated for > this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4503) [Core R6] Support osgi.native capability
[ https://issues.apache.org/jira/browse/FELIX-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241252#comment-14241252 ] David Bosschaert commented on FELIX-4503: - Hi Bob, I'm not sure what the background of those Java 6 failures with native code are, maybe Richard remembers, but I guess you could try it with Java 5 and/or 7. When I ran the CT I used Java 7, so that might have cause some of these failures above... > [Core R6] Support osgi.native capability > > > Key: FELIX-4503 > URL: https://issues.apache.org/jira/browse/FELIX-4503 > Project: Felix > Issue Type: Sub-task > Components: Framework >Affects Versions: framework-4.4.0 >Reporter: David Bosschaert >Assignee: Bob Paulin > Fix For: framework-4.6.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4503) [Core R6] Support osgi.native capability
[ https://issues.apache.org/jira/browse/FELIX-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241246#comment-14241246 ] Bob Paulin commented on FELIX-4503: --- Hi David. I started looking at those a bit last week. I should be able to do some more digging at the end of this week. For the test documentation there is a warning about using java6: Be Aware Tests for native code loading will fail on Java 6, so do not use this JDK for testing the framework. Does that still apply? > [Core R6] Support osgi.native capability > > > Key: FELIX-4503 > URL: https://issues.apache.org/jira/browse/FELIX-4503 > Project: Felix > Issue Type: Sub-task > Components: Framework >Affects Versions: framework-4.4.0 >Reporter: David Bosschaert >Assignee: Bob Paulin > Fix For: framework-4.6.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4726) [Core R6] Update bundle and service hooks for the system bundle
David Bosschaert created FELIX-4726: --- Summary: [Core R6] Update bundle and service hooks for the system bundle Key: FELIX-4726 URL: https://issues.apache.org/jira/browse/FELIX-4726 Project: Felix Issue Type: Sub-task Components: Framework Reporter: David Bosschaert Assignee: David Bosschaert Fix For: framework-4.6.0 The Core R6 spec has updates around Bundle and Service Hook behaviour in relation to the system bundle. The Felix framework needs to be updated for this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (FELIX-4503) [Core R6] Support osgi.native capability
[ https://issues.apache.org/jira/browse/FELIX-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert reopened FELIX-4503: - I'm reopening this issue because in the Core R6 CT there are a lot of failures around native code, which I'm guessing relate to this issue: The following tests in DivTests fail: testNativeCode() testNativeCodeFilterOptional() testNativeCodeFilterNoOptional() testNativeCodeFilterAlias() testNativeCodeFragment() testNativeCodeLanguage() testNativeCodeLanguageSuccess() testNativeCodeVersion() testNativeCodeVersionSuccess() testNativeCodeNamespaceRequirement() testNativeCodeNamespaceCapability() Bob, would you have a moment to take a look? > [Core R6] Support osgi.native capability > > > Key: FELIX-4503 > URL: https://issues.apache.org/jira/browse/FELIX-4503 > Project: Felix > Issue Type: Sub-task > Components: Framework >Affects Versions: framework-4.4.0 >Reporter: David Bosschaert >Assignee: Bob Paulin > Fix For: framework-4.6.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4583) [Core R6] Ensure that all OSGi Core R6 CT tests pass
[ https://issues.apache.org/jira/browse/FELIX-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241207#comment-14241207 ] David Bosschaert commented on FELIX-4583: - There is one known deviation in the Core R6 CT: DTOTestCase.testArrayServiceReferenceDTO() fails, but the implementation in Felix is actually correct. > [Core R6] Ensure that all OSGi Core R6 CT tests pass > > > Key: FELIX-4583 > URL: https://issues.apache.org/jira/browse/FELIX-4583 > Project: Felix > Issue Type: Sub-task > Components: Framework >Reporter: David Bosschaert >Assignee: David Bosschaert > Fix For: framework-4.6.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4502) [Core R6] Provide an OSGi R6 compliant framework implementation
[ https://issues.apache.org/jira/browse/FELIX-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated FELIX-4502: Assignee: (was: David Bosschaert) > [Core R6] Provide an OSGi R6 compliant framework implementation > --- > > Key: FELIX-4502 > URL: https://issues.apache.org/jira/browse/FELIX-4502 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-4.4.0 >Reporter: David Bosschaert > Fix For: framework-4.6.0 > > > OSGi Core R6 compliance needs to be provided. > This is an umbrella issue to track the necessary tasks to make Felix R6 > compliant. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (FELIX-4583) [Core R6] Ensure that all OSGi Core R6 CT tests pass
[ https://issues.apache.org/jira/browse/FELIX-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-4583 started by David Bosschaert. --- > [Core R6] Ensure that all OSGi Core R6 CT tests pass > > > Key: FELIX-4583 > URL: https://issues.apache.org/jira/browse/FELIX-4583 > Project: Felix > Issue Type: Sub-task > Components: Framework >Reporter: David Bosschaert >Assignee: David Bosschaert > Fix For: framework-4.6.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FELIX-4502) [Core R6] Provide an OSGi R6 compliant framework implementation
[ https://issues.apache.org/jira/browse/FELIX-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert reassigned FELIX-4502: --- Assignee: David Bosschaert > [Core R6] Provide an OSGi R6 compliant framework implementation > --- > > Key: FELIX-4502 > URL: https://issues.apache.org/jira/browse/FELIX-4502 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-4.4.0 >Reporter: David Bosschaert >Assignee: David Bosschaert > Fix For: framework-4.6.0 > > > OSGi Core R6 compliance needs to be provided. > This is an umbrella issue to track the necessary tasks to make Felix R6 > compliant. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FELIX-4583) [Core R6] Ensure that all OSGi Core R6 CT tests pass
[ https://issues.apache.org/jira/browse/FELIX-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert reassigned FELIX-4583: --- Assignee: David Bosschaert > [Core R6] Ensure that all OSGi Core R6 CT tests pass > > > Key: FELIX-4583 > URL: https://issues.apache.org/jira/browse/FELIX-4583 > Project: Felix > Issue Type: Sub-task > Components: Framework >Reporter: David Bosschaert >Assignee: David Bosschaert > Fix For: framework-4.6.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (FELIX-4502) [Core R6] Provide an OSGi R6 compliant framework implementation
[ https://issues.apache.org/jira/browse/FELIX-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-4502 started by David Bosschaert. --- > [Core R6] Provide an OSGi R6 compliant framework implementation > --- > > Key: FELIX-4502 > URL: https://issues.apache.org/jira/browse/FELIX-4502 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-4.4.0 >Reporter: David Bosschaert >Assignee: David Bosschaert > Fix For: framework-4.6.0 > > > OSGi Core R6 compliance needs to be provided. > This is an umbrella issue to track the necessary tasks to make Felix R6 > compliant. -- 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=14241202#comment-14241202 ] Peter Kriens commented on FELIX-4720: - It feels a bit like I am on candid camera :-) In the end the user sees that Gogo & Webconsole do not work against a valid OSGi implementation of Log (Reader) Service that passes the TCK I'll provide a patch because as Carsten says this discussion is taking me more time than fixing it :-( > 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
+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 > > 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 >> > > > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org
Re: [VOTE] Release Apache Felix Web Console 4.2.4
+1, Regards, Clement On 10 décembre 2014 at 14:58:11, Carsten Ziegeler (cziege...@apache.org) wrote: +1 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 > -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: [VOTE] Release Apache Felix Web Console 4.2.4
+1 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 > -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: [VOTE] Release Apache Felix Web Console 4.2.4
On Wednesday, 10 December 2014 at 12:32, Valentin Valchev wrote: > 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 (http://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.) > > It’s the number allocated to the staging repository by Nexus If you log into RAO and open: https://repository.apache.org/index.html#stagingRepositories then you should see your staged repository In this case it’s "orgapachefelix-1045” so the number to use with the script is 1045 The summary tab that appears when you click on the repository gives the staging repository URL containing just your content: https://repository.apache.org/content/repositories/orgapachefelix-1045 Also note that https://repository.apache.org/content/groups/staging/... groups the content from all current staging repositories. Some people prefer to use the specific staging repository in the vote thread, but the staging group repository can be useful when you want to test a combination of staged releases. > > 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 (mailto:v.valc...@prosyst.bg) > - > stay in touch with your product. > - > > > > > Attachments: > - v_valchev.vcf >
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
Re: [VOTE] Release Apache Felix Web Console 4.2.4
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 > -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[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=14240857#comment-14240857 ] Carsten Ziegeler commented on FELIX-4720: - [~v_valchev] I think we agree on these points - however if a valid log service implementation can provide an empty history we can do something about this; and we can do it in a way that there is no change for systems with a buffering log service implementation. > 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=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)
