Re: [VOTE] Release iPOJO WebConsole Plugin 1.6.0
+1 Regards Felix Am Sonntag, den 30.01.2011, 18:35 + schrieb Clement Escoffier: > Hello, > > > It's a long time due release. I've cut a release of the iPOJO WebConsole > plugin improving the integration inside the webconsole 3.x. It does not > introduce new features, just a major refactoring and redevelopment of the > plugin to fit the new architecture. It's the 1.6.0 version but also works > with iPOJO 1.4.0 and 1.8.0 (detached development). > > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-002/ > > 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 002 /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, > > > Clement > >
[jira] Commented: (FELIX-2817) The maven-bundle-plugin manifest goal should honor the supportedProjectTypes configuration setting.
[ https://issues.apache.org/jira/browse/FELIX-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989505#comment-12989505 ] Andreas Pieber commented on FELIX-2817: --- Maybe I'm wrong but 2.3 is the wrong target version, since it is already for vote? > The maven-bundle-plugin manifest goal should honor the supportedProjectTypes > configuration setting. > --- > > Key: FELIX-2817 > URL: https://issues.apache.org/jira/browse/FELIX-2817 > Project: Felix > Issue Type: Bug >Affects Versions: maven-bundle-plugin-2.2.0 >Reporter: Hiram Chirino >Assignee: Hiram Chirino > Fix For: maven-bundle-plugin-2.3.0 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (FELIX-2817) The maven-bundle-plugin manifest goal should honor the supportedProjectTypes configuration setting.
[ https://issues.apache.org/jira/browse/FELIX-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino resolved FELIX-2817. -- Resolution: Fixed Fixed in rev 1066202 > The maven-bundle-plugin manifest goal should honor the supportedProjectTypes > configuration setting. > --- > > Key: FELIX-2817 > URL: https://issues.apache.org/jira/browse/FELIX-2817 > Project: Felix > Issue Type: Bug >Affects Versions: maven-bundle-plugin-2.2.0 >Reporter: Hiram Chirino >Assignee: Hiram Chirino > Fix For: maven-bundle-plugin-2.3.0 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FELIX-2817) The maven-bundle-plugin manifest goal should honor the supportedProjectTypes configuration setting.
The maven-bundle-plugin manifest goal should honor the supportedProjectTypes configuration setting. --- Key: FELIX-2817 URL: https://issues.apache.org/jira/browse/FELIX-2817 Project: Felix Issue Type: Bug Affects Versions: maven-bundle-plugin-2.2.0 Reporter: Hiram Chirino Assignee: Hiram Chirino Fix For: maven-bundle-plugin-2.3.0 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release webconsole 3.1.8
+1, Regards, Clement On 01.02.11 09:16, "Guillaume Nodet" wrote: >This release fixes several issues >* [FELIX-2713] - Problem in HtmlConfigurationWriter >* [FELIX-2729] - Webconsole - Configuration fails to print >configuration for bundles without MetatypeService config >* [FELIX-2735] - ClassCastException in PermissionsConfigurationPrinter >* [FELIX-2793] - Plugin request is not detected as html request if >context path contains a dot >* [FELIX-2795] - Parameters are not removed from symbolic name >when installing a bundle > >The staging repo is available at: > https://repository.apache.org/content/repositories/orgapachefelix-023/ > >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 023 /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. > >-- >Cheers, >Guillaume Nodet > >Blog: http://gnodet.blogspot.com/ > >Open Source SOA >http://fusesource.com
Re: [VOTE] Release webconsole 3.1.8
+1 kind regards, andreas On Tue, Feb 01, 2011 at 09:16:20AM +0100, Guillaume Nodet wrote: > This release fixes several issues > * [FELIX-2713] - Problem in HtmlConfigurationWriter > * [FELIX-2729] - Webconsole - Configuration fails to print > configuration for bundles without MetatypeService config > * [FELIX-2735] - ClassCastException in PermissionsConfigurationPrinter > * [FELIX-2793] - Plugin request is not detected as html request if > context path contains a dot > * [FELIX-2795] - Parameters are not removed from symbolic name > when installing a bundle > > The staging repo is available at: > https://repository.apache.org/content/repositories/orgapachefelix-023/ > > 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 023 /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. > > -- > Cheers, > Guillaume Nodet > > Blog: http://gnodet.blogspot.com/ > > Open Source SOA > http://fusesource.com pgpCDZTp8JEU4.pgp Description: PGP signature
Re: [VOTE] Release webconsole 3.1.8
On 2/1/11 13:58, Carsten Ziegeler wrote: Richard S. Hall wrote The copyright year wasn't updated...I can't remember, do we consider this a big deal or not? No, we don't :) Ok, then: +1 Please update the copyright years in the NOTICE and DEPENDENCIES files in trunk. -> richard Carsten -> richard On 2/1/11 3:16, Guillaume Nodet wrote: This release fixes several issues * [FELIX-2713] - Problem in HtmlConfigurationWriter * [FELIX-2729] - Webconsole - Configuration fails to print configuration for bundles without MetatypeService config * [FELIX-2735] - ClassCastException in PermissionsConfigurationPrinter * [FELIX-2793] - Plugin request is not detected as html request if context path contains a dot * [FELIX-2795] - Parameters are not removed from symbolic name when installing a bundle The staging repo is available at: https://repository.apache.org/content/repositories/orgapachefelix-023/ 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 023 /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.
Re: [VOTE] Release webconsole 3.1.8
+1 Regards JB On 02/01/2011 09:16 AM, Guillaume Nodet wrote: This release fixes several issues * [FELIX-2713] - Problem in HtmlConfigurationWriter * [FELIX-2729] - Webconsole - Configuration fails to print configuration for bundles without MetatypeService config * [FELIX-2735] - ClassCastException in PermissionsConfigurationPrinter * [FELIX-2793] - Plugin request is not detected as html request if context path contains a dot * [FELIX-2795] - Parameters are not removed from symbolic name when installing a bundle The staging repo is available at: https://repository.apache.org/content/repositories/orgapachefelix-023/ 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 023 /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. -- Jean-Baptiste Onofré - HomePage http://www.nanthrax.net - Contacts jbono...@apache.org j...@nanthrax.net - OpenSource BuildProcess/AutoDeploy http://buildprocess.sourceforge.net Apache ServiceMix http://servicemix.apache.org --- PGP : 17D4F086
Re: [VOTE] Release webconsole 3.1.8
+1 Carsten Guillaume Nodet wrote > This release fixes several issues > * [FELIX-2713] - Problem in HtmlConfigurationWriter > * [FELIX-2729] - Webconsole - Configuration fails to print > configuration for bundles without MetatypeService config > * [FELIX-2735] - ClassCastException in PermissionsConfigurationPrinter > * [FELIX-2793] - Plugin request is not detected as html request if > context path contains a dot > * [FELIX-2795] - Parameters are not removed from symbolic name > when installing a bundle > > The staging repo is available at: > https://repository.apache.org/content/repositories/orgapachefelix-023/ > > 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 023 /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. > -- Carsten Ziegeler cziege...@apache.org
Re: [VOTE] Release webconsole 3.1.8
Richard S. Hall wrote > The copyright year wasn't updated...I can't remember, do we consider > this a big deal or not? No, we don't :) Carsten > > -> richard > > > On 2/1/11 3:16, Guillaume Nodet wrote: >> This release fixes several issues >> * [FELIX-2713] - Problem in HtmlConfigurationWriter >> * [FELIX-2729] - Webconsole - Configuration fails to print >> configuration for bundles without MetatypeService config >> * [FELIX-2735] - ClassCastException in >> PermissionsConfigurationPrinter >> * [FELIX-2793] - Plugin request is not detected as html request if >> context path contains a dot >> * [FELIX-2795] - Parameters are not removed from symbolic name >> when installing a bundle >> >> The staging repo is available at: >> https://repository.apache.org/content/repositories/orgapachefelix-023/ >> >> 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 023 /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. >> > -- Carsten Ziegeler cziege...@apache.org
Re: [VOTE] Release iPOJO WebConsole Plugin 1.6.0
+1, Regards, Clement From: Clement Escoffier Date: Sun, 30 Jan 2011 19:35:59 +0100 To: Apache Felix - Developpers Mailing List Subject: [VOTE] Release iPOJO WebConsole Plugin 1.6.0 > Hello, > > > It's a long time due release. I've cut a release of the iPOJO WebConsole > plugin improving the integration inside the webconsole 3.x. It does not > introduce new features, just a major refactoring and redevelopment of the > plugin to fit the new architecture. It's the 1.6.0 version but also works with > iPOJO 1.4.0 and 1.8.0 (detached development). > > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-002/ > > 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 002 /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, > > > Clement
[jira] Resolved: (FELIX-2815) Difference between "instance" and "provides"
[ https://issues.apache.org/jira/browse/FELIX-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier resolved FELIX-2815. -- Resolution: Fixed I've updated the page (will be sync soon). I've added an example describing what is instance reconfiguration and how it does impact the published service properties. > Difference between "instance" and "provides" > > > Key: FELIX-2815 > URL: https://issues.apache.org/jira/browse/FELIX-2815 > Project: Felix > Issue Type: Bug > Components: iPOJO >Reporter: Andriyko >Assignee: Clement Escoffier > Labels: documentation, felix,, ipojo > > In the documentation on iPOJO Services: > http://felix.apache.org/site/providing-osgi-services.html#ProvidingOSGiservices-Instancereconfiguration > There is no clear explanation of what is the difference between > and . > It is not clear why "instance" is needed at all. > Under the "Service Properties" heading on the page, the two are used > interchangeably in the examples. > For example, first "property" is configured with : > > > > value="this is a static property"/> > > > and then immediately, with no explanation what-so-ever and is > used, with a tiny explanation that "The value can be given in the instance > configuration": > > > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FELIX-2815) Difference between "instance" and "provides"
[ https://issues.apache.org/jira/browse/FELIX-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier updated FELIX-2815: - Component/s: (was: Felix Commons) iPOJO Assignee: Clement Escoffier > Difference between "instance" and "provides" > > > Key: FELIX-2815 > URL: https://issues.apache.org/jira/browse/FELIX-2815 > Project: Felix > Issue Type: Bug > Components: iPOJO >Reporter: Andriyko >Assignee: Clement Escoffier > Labels: documentation, felix,, ipojo > > In the documentation on iPOJO Services: > http://felix.apache.org/site/providing-osgi-services.html#ProvidingOSGiservices-Instancereconfiguration > There is no clear explanation of what is the difference between > and . > It is not clear why "instance" is needed at all. > Under the "Service Properties" heading on the page, the two are used > interchangeably in the examples. > For example, first "property" is configured with : > > > > value="this is a static property"/> > > > and then immediately, with no explanation what-so-ever and is > used, with a tiny explanation that "The value can be given in the instance > configuration": > > > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FELIX-2814) Spelling Mistake
[ https://issues.apache.org/jira/browse/FELIX-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier updated FELIX-2814: - Component/s: (was: Felix Commons) iPOJO > Spelling Mistake > > > Key: FELIX-2814 > URL: https://issues.apache.org/jira/browse/FELIX-2814 > Project: Felix > Issue Type: Bug > Components: iPOJO >Reporter: Andriyko >Assignee: Clement Escoffier > Labels: documentaion, felix,, osgi, > > Please excuse my spelling bug-reports, but it really bothers me to read this. > On the documentation page: > http://felix.apache.org/site/providing-osgi-services.html#ProvidingOSGiservices-Instancereconfiguration > Under "Service Publication" section, first paragraph: > 1. "The provided service handler manages the service publication and > providing". I think "providing" is not a correct word to use here. > 2. "For each declared , the handler register a service.". And it > should be "registers". > 3. "As the @Provides annotation can be used only once, only on service is > registered (but publishing all interfaces)." - There are two mistakes here: > first, change "on" to "one", second - "but publishing all interfaces" I think > should be changed to "but all interfaces are published". > In the second paragraph, last sentence: > 1. "However it is possible to set exposed specifications with the > specifications attribute to avoid to expose all collected interfaces". I > think "to avoid to expose all" should be changed to "to avoid exposing > all...". Also - this sentence is very confusing in general - is it possible > to simplify it? > Furthermore, following the code sample after this paragraph, the three change > notices (blue boxes) are not left-aligned. I don't know if it is like that > intentionally or not. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (FELIX-2814) Spelling Mistake
[ https://issues.apache.org/jira/browse/FELIX-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier resolved FELIX-2814. -- Resolution: Fixed Assignee: Clement Escoffier Richard has fixed the issues. It will be updated during the next sync. Thanks ! Clement > Spelling Mistake > > > Key: FELIX-2814 > URL: https://issues.apache.org/jira/browse/FELIX-2814 > Project: Felix > Issue Type: Bug > Components: Felix Commons >Reporter: Andriyko >Assignee: Clement Escoffier > Labels: documentaion, felix,, osgi, > > Please excuse my spelling bug-reports, but it really bothers me to read this. > On the documentation page: > http://felix.apache.org/site/providing-osgi-services.html#ProvidingOSGiservices-Instancereconfiguration > Under "Service Publication" section, first paragraph: > 1. "The provided service handler manages the service publication and > providing". I think "providing" is not a correct word to use here. > 2. "For each declared , the handler register a service.". And it > should be "registers". > 3. "As the @Provides annotation can be used only once, only on service is > registered (but publishing all interfaces)." - There are two mistakes here: > first, change "on" to "one", second - "but publishing all interfaces" I think > should be changed to "but all interfaces are published". > In the second paragraph, last sentence: > 1. "However it is possible to set exposed specifications with the > specifications attribute to avoid to expose all collected interfaces". I > think "to avoid to expose all" should be changed to "to avoid exposing > all...". Also - this sentence is very confusing in general - is it possible > to simplify it? > Furthermore, following the code sample after this paragraph, the three change > notices (blue boxes) are not left-aligned. I don't know if it is like that > intentionally or not. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Felix framework 3.0.8 and related subproject releases
+1, Regards, Clement On 30.01.11 22:18, "Karl Pauls" wrote: >I would like to call a vote on the following subproject releases: > >framework 3.0.8 >main 3.0.8 >main.distribution 3.0.8 > >Staging repositories: >https://repository.apache.org/content/repositories/orgapachefelix-011/ > >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 011 /tmp/felix-staging > >Please vote to approve this release: > >[ ] +1 Approve the release >[ ] -1 Veto the release (please provide specific comments)
Re: [VOTE] Felix framework 3.0.8 and related subproject releases
+1 Regards Felix Am Sonntag, den 30.01.2011, 21:18 + schrieb Karl Pauls: > I would like to call a vote on the following subproject releases: > > framework 3.0.8 > main 3.0.8 > main.distribution 3.0.8 > > Staging repositories: > https://repository.apache.org/content/repositories/orgapachefelix-011/ > > 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 011 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments)
Re: [VOTE] Release webconsole 3.1.8
The copyright year wasn't updated...I can't remember, do we consider this a big deal or not? -> richard On 2/1/11 3:16, Guillaume Nodet wrote: This release fixes several issues * [FELIX-2713] - Problem in HtmlConfigurationWriter * [FELIX-2729] - Webconsole - Configuration fails to print configuration for bundles without MetatypeService config * [FELIX-2735] - ClassCastException in PermissionsConfigurationPrinter * [FELIX-2793] - Plugin request is not detected as html request if context path contains a dot * [FELIX-2795] - Parameters are not removed from symbolic name when installing a bundle The staging repo is available at: https://repository.apache.org/content/repositories/orgapachefelix-023/ 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 023 /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.
Re: [VOTE] Release maven-bundle-plugin 2.3.0
The NOTICE file wasn't updated and no DEPENDENCIES file. -> richard On 1/31/11 11:45, Guillaume Nodet wrote: I would like to call a vote on the maven-bundle-plugin 2.3.0 release: Staging repositories: https://repository.apache.org/content/repositories/orgapachefelix-020/ Changelog: https://issues.apache.org/jira/secure/ReleaseNote.jspa?atl_token=8d589633a054278ec7f36db6fcb02560518a1b8f&version=12316061&styleName=Text&projectId=12310100&Create=Create 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 020 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments)
Re: [VOTE] Release iPOJO WebConsole Plugin 1.6.0
+1 -> richard On 1/30/11 13:35, Clement Escoffier wrote: Hello, It's a long time due release. I've cut a release of the iPOJO WebConsole plugin improving the integration inside the webconsole 3.x. It does not introduce new features, just a major refactoring and redevelopment of the plugin to fit the new architecture. It's the 1.6.0 version but also works with iPOJO 1.4.0 and 1.8.0 (detached development). Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-002/ 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 002 /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, Clement
Re: [VOTE] Release fileinstall-3.1.8 (2nd try)
+1 -> richard On 1/31/11 3:34, Guillaume Nodet wrote: Same as before, but the release actually contains both fixes and an updated changelog This release fixes two issues https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310100&fixfor=12316099 * FELIX-2799 FileInstall creates multiple configurations for factory configurations on windows * FELIX-2798 ArtifactListener services are not ordered according to the OSGi ranking The staging repo is available at: https://repository.apache.org/content/repositories/orgapachefelix-017/ 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 017 /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.
Re: [VOTE] Felix framework 3.0.8 and related subproject releases
+1 -> richard On 1/30/11 16:18, Karl Pauls wrote: I would like to call a vote on the following subproject releases: framework 3.0.8 main 3.0.8 main.distribution 3.0.8 Staging repositories: https://repository.apache.org/content/repositories/orgapachefelix-011/ 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 011 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments)
[jira] Closed: (FELIX-2779) iPOJO manipulator badly supports custom annotation attributes of type Class
[
https://issues.apache.org/jira/browse/FELIX-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Bourret closed FELIX-2779.
-
OK : tested with iPOJO-1.8.0
> iPOJO manipulator badly supports custom annotation attributes of type Class
> ---
>
> Key: FELIX-2779
> URL: https://issues.apache.org/jira/browse/FELIX-2779
> Project: Felix
> Issue Type: Bug
> Components: iPOJO
>Affects Versions: iPOJO-1.6.0
>Reporter: Pierre Bourret
>Assignee: Clement Escoffier
>Priority: Minor
> Fix For: iPOJO-1.8.0
>
> Attachments:
> FixBadClassParameterHandlingInCustomAnnotationVisitor.patch
>
>
> I've written a custom handler and its corresponding annotation :
>public @interface Portlet {
> ...
> Class portletClass();
> ...
>}
> Then I've defined a component using this annotation :
>@Component
>@Portlet(..., portletClass=DummyComponentPortletImpl.class)
>public class DummyComponentImpl {
> ...
>}
> The problem is that the metadata computed by the manipulator doesn't hold the
> right value for the portletClass attribute :
> I got "Lfr/liglab/adele/icasa/portal/impl/test/DummyComponentPortletImpl;"
> instead of "fr.liglab.adele.icasa.portal.impl.test.DummyComponentPortletImpl".
> Despite it is still possible to deduce the original class name from this
> strange string, isn't the attribute value supposed to contain the real class
> name instead of a Java internal type name ?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (FELIX-2813) NPE in UpdateThread when updating a configuration right after ConfigurationAdmin service starts
[ https://issues.apache.org/jira/browse/FELIX-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved FELIX-2813. -- Resolution: Fixed Fix Version/s: configadmin-1.2.10 Assignee: Felix Meschberger Committed a fix in Rev. 1066033. Besides making the service registration field volatile (as proposed) the background threads are started after registering the service (though jobs may be enqueued during the service registration) and are stopped before the service is unregistered. > NPE in UpdateThread when updating a configuration right after > ConfigurationAdmin service starts > --- > > Key: FELIX-2813 > URL: https://issues.apache.org/jira/browse/FELIX-2813 > Project: Felix > Issue Type: Bug > Components: Configuration Admin >Reporter: Marcel Offermans >Assignee: Felix Meschberger > Fix For: configadmin-1.2.10 > > > When you: > 1) register as a configuration listener > 2) wait for the ConfigurationAdmin service to start > 3) upon start, immediately create a new configuration and update its > properties > You (sometimes) get a NPE in the UpdateThread because there is a race > condition in the codebase: > a) ConfigurationManager.java:1818 will invoke getServiceReference() which > uses the service registration to get to the reference > b) ConfigurationManager.java:242 registers the service and assigns the > registration to 'configurationAdminRegistration' > First of all, the call to registerService in line 242 will already trigger > service listeners and trackers to invoke callbacks before this call returns, > so 'configurationAdminRegistration' will still be null. Furthermore, there is > no synchronization, the member is not volatile, so we need to make sure this > value is really written before any configuration events are created under a) > (now the thread doing that is started way before the service is registered). > I will commit a test that shows the exception, but since it happens in a > thread I cannot "catch" it won't show up as a failed test. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FELIX-2813) NPE in UpdateThread when updating a configuration right after ConfigurationAdmin service starts
[ https://issues.apache.org/jira/browse/FELIX-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989180#comment-12989180 ] Felix Meschberger commented on FELIX-2813: -- Yes, the ConfigurationEvent is actually generated immediately before sending it out. So just enqueuing the task to send the event is save. > NPE in UpdateThread when updating a configuration right after > ConfigurationAdmin service starts > --- > > Key: FELIX-2813 > URL: https://issues.apache.org/jira/browse/FELIX-2813 > Project: Felix > Issue Type: Bug > Components: Configuration Admin >Reporter: Marcel Offermans > > When you: > 1) register as a configuration listener > 2) wait for the ConfigurationAdmin service to start > 3) upon start, immediately create a new configuration and update its > properties > You (sometimes) get a NPE in the UpdateThread because there is a race > condition in the codebase: > a) ConfigurationManager.java:1818 will invoke getServiceReference() which > uses the service registration to get to the reference > b) ConfigurationManager.java:242 registers the service and assigns the > registration to 'configurationAdminRegistration' > First of all, the call to registerService in line 242 will already trigger > service listeners and trackers to invoke callbacks before this call returns, > so 'configurationAdminRegistration' will still be null. Furthermore, there is > no synchronization, the member is not volatile, so we need to make sure this > value is really written before any configuration events are created under a) > (now the thread doing that is started way before the service is registered). > I will commit a test that shows the exception, but since it happens in a > thread I cannot "catch" it won't show up as a failed test. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FELIX-2813) NPE in UpdateThread when updating a configuration right after ConfigurationAdmin service starts
[ https://issues.apache.org/jira/browse/FELIX-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989101#comment-12989101 ] Marcel Offermans commented on FELIX-2813: - Take care that the service reference is fetched when an event is created, so even if you delay processing the queue it might be that there's invalid events in there. > NPE in UpdateThread when updating a configuration right after > ConfigurationAdmin service starts > --- > > Key: FELIX-2813 > URL: https://issues.apache.org/jira/browse/FELIX-2813 > Project: Felix > Issue Type: Bug > Components: Configuration Admin >Reporter: Marcel Offermans > > When you: > 1) register as a configuration listener > 2) wait for the ConfigurationAdmin service to start > 3) upon start, immediately create a new configuration and update its > properties > You (sometimes) get a NPE in the UpdateThread because there is a race > condition in the codebase: > a) ConfigurationManager.java:1818 will invoke getServiceReference() which > uses the service registration to get to the reference > b) ConfigurationManager.java:242 registers the service and assigns the > registration to 'configurationAdminRegistration' > First of all, the call to registerService in line 242 will already trigger > service listeners and trackers to invoke callbacks before this call returns, > so 'configurationAdminRegistration' will still be null. Furthermore, there is > no synchronization, the member is not volatile, so we need to make sure this > value is really written before any configuration events are created under a) > (now the thread doing that is started way before the service is registered). > I will commit a test that shows the exception, but since it happens in a > thread I cannot "catch" it won't show up as a failed test. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FELIX-2813) NPE in UpdateThread when updating a configuration right after ConfigurationAdmin service starts
[ https://issues.apache.org/jira/browse/FELIX-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989094#comment-12989094 ] Felix Meschberger commented on FELIX-2813: -- Thanks for reporting the bug. First of all declaring the configurationAdminRegistration volatile should help your concerns with the getServiceReference() method; particularly with respect to logging. On the other hand for the getServiceReference() method itself, this is irrelelvant. Second the other issue is in fact not properly handled but easily fixed: Instead of immediately starting the worker threads for the UpdateQueue instances, we delay the start until after the ConfigurationAdmin service has been fully registered. This allows for events to be queued during the service registration process (by ServiceListeners) and to actually process them after completion of the registration. This problem has a symmetry in the ConfigurationManager.stop(BundleContext) method: Here the queues should be stopped before unregistering the ConfigurationAdmin service to not get an NPE if a ServiceListener is updating/deleting configuration in the serviceStopped method. > NPE in UpdateThread when updating a configuration right after > ConfigurationAdmin service starts > --- > > Key: FELIX-2813 > URL: https://issues.apache.org/jira/browse/FELIX-2813 > Project: Felix > Issue Type: Bug > Components: Configuration Admin >Reporter: Marcel Offermans > > When you: > 1) register as a configuration listener > 2) wait for the ConfigurationAdmin service to start > 3) upon start, immediately create a new configuration and update its > properties > You (sometimes) get a NPE in the UpdateThread because there is a race > condition in the codebase: > a) ConfigurationManager.java:1818 will invoke getServiceReference() which > uses the service registration to get to the reference > b) ConfigurationManager.java:242 registers the service and assigns the > registration to 'configurationAdminRegistration' > First of all, the call to registerService in line 242 will already trigger > service listeners and trackers to invoke callbacks before this call returns, > so 'configurationAdminRegistration' will still be null. Furthermore, there is > no synchronization, the member is not volatile, so we need to make sure this > value is really written before any configuration events are created under a) > (now the thread doing that is started way before the service is registered). > I will commit a test that shows the exception, but since it happens in a > thread I cannot "catch" it won't show up as a failed test. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[VOTE] Release webconsole 3.1.8
This release fixes several issues * [FELIX-2713] - Problem in HtmlConfigurationWriter * [FELIX-2729] - Webconsole - Configuration fails to print configuration for bundles without MetatypeService config * [FELIX-2735] - ClassCastException in PermissionsConfigurationPrinter * [FELIX-2793] - Plugin request is not detected as html request if context path contains a dot * [FELIX-2795] - Parameters are not removed from symbolic name when installing a bundle The staging repo is available at: https://repository.apache.org/content/repositories/orgapachefelix-023/ 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 023 /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. -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
