[jira] [Commented] (FELIX-4069) ConcurrentModificationException in ServiceFactoryComponentManager
[ https://issues.apache.org/jira/browse/FELIX-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663288#comment-13663288 ] Adam Purkiss commented on FELIX-4069: - The error does not seem to occur and things seem ok at the moment although we will continue testing with this, I have not looked at the full change list from 1.6.2 to this so I am assuming all should be good else where. Is there a eta on when this might make it to an official update? On a side not I had to skip the unit tests on my dev box when doing the build as I got a build failure during the tests . I have not looked into the test failure to see what is going on but for your information my dev box was saying: [org.apache.felix.scr.integration.components.concurrency.C] (exit) log level: 4 D=13:20:10,796 T=Thread[Thread-4,5,main]: [org.apache.felix.scr.int egration.components.concurrency.C(21310)] Unset and deconfigured implementation object for component org.apache.felix.scr.integration.components.concurrency.C i n deleteComponent for reason Component disabled log level: 4 D=13:20:10,796 T=Thread[Thread-4,5,main]: [org.apache.felix.scr.int egration.components.concurrency.C(21310)] Deactivating dependency managers log level: 4 D=13:20:10,796 T=Thread[Thread-4,5,main]: [org.apache.felix.scr.int egration.components.concurrency.C(21310)] Disabling dependency managers Results : Tests run: 17, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 8:16.128s [INFO] Finished at: Tue May 21 13:27:10 EDT 2013 [INFO] Final Memory: 12M/247M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2. 12:integration-test (default) on project org.apache.felix.scr: Execution default of goal org.apache.maven.plugins:maven-failsafe-plugin:2.12:integration-test fa iled: The forked VM terminated without saying properly goodbye. VM crash or Syst em.exit called ? -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit ch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please rea d the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutio nException > ConcurrentModificationException in ServiceFactoryComponentManager > - > > Key: FELIX-4069 > URL: https://issues.apache.org/jira/browse/FELIX-4069 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) >Affects Versions: scr-1.6.2 > Environment: Windows 7 >Reporter: Adam Purkiss >Assignee: David Jencks > Fix For: scr-1.8.0 > > > During startup of our application that is heavily dependant on DS and felix > we occasionally see the following error: > ERROR: Bundle DwsCoreImpl.DwsCoreLogProviderImpl [37] EventDispatcher: Error > during dispatch. (java.util.ConcurrentModificationException) > java.util.ConcurrentModificationException > at > java.util.IdentityHashMap$IdentityHashMapIterator.nextIndex(IdentityHashMap.java:732) > at > java.util.IdentityHashMap$KeyIterator.next(IdentityHashMap.java:822) > at > org.apache.felix.scr.impl.manager.ServiceFactoryComponentManager.invokeBindMethod(ServiceFactoryComponentManager.java:204) > at > org.apache.felix.scr.impl.manager.DependencyManager.serviceAdded(DependencyManager.java:402) > at > org.apache.felix.scr.impl.manager.DependencyManager.serviceChanged(DependencyManager.java:159) > at > org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932) > at > org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793) > at > org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543) > at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4419) > at org.apache.felix.framework.Felix.registerService(Felix.java:3423) > at > org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346) > at > org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:660) > at > org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:644) > at > org.apache.felix.scr.impl.manager.AbstractComponentManager.registerComponentService(AbstractComponentManager.java:688) > at
Re: [VOTE] Release of iPOJO Manipulator 1.10.0, iPOJO Runtime 1.10.0, iPOJO Gogo Command 1.1.0 and iPOJO's Web Console Plugin (1.7.0)
+1 -> richard On 5/15/13 13:14 , Clement Escoffier wrote: Hi, It's time to cut a release of the iPOJO manipulator (1.10.0), runtime project (1.10.0), Gogo's architecture command (1.1.0) and iPOJO Web Console plugin (1.7.0). This releases contains: * bnd-ipojo-plugin - 1.10.0 * maven-ipojo-plugin - 1.10.0 * org.apache.felix.ipojo - 1.10.0 * org.apache.felix.ipojo.annotations - 1.10.0 * org.apache.felix.ipojo.ant - 1.10.0 * org.apache.felix.ipojo.api - 1.10.0 * org.apache.felix.ipojo.arch.gogo - 1.1.0 * org.apache.felix.ipojo.composite - 1.10.0 * org.apache.felix.ipojo.manipulator - 1.10.0 * org.apache.felix.ipojo.manipulator-project - 1.10.0 * org.apache.felix.ipojo.manipulator.online - 1.10.0 * org.apache.felix.ipojo.runtime-project - 1.10.0 * org.apache.felix.ipojo.webconsole - 1.7.0 Those releases contain a lot of bug fixes, improvements and new feature. The changelogs are below. Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-024/ 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 024 /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 (at least). Regards, Clement Changelog of the manipulator project (1.10.0): ** Bug * [FELIX-3827] - Error in bbd-ipojo-plugin of manipulating jar with embedded dependencies with maven bundle plugin + bnd-ipojo-plugin * [FELIX-3900] - @HandlerDeclaration do not convert DOM Attributes to iPOJO Attributes correctly * [FELIX-3938] - maven-ipojo-plugin does not behave as bnd-ipojo-plugin * [FELIX-3974] - Properties cannot be set as immutable using annotations * [FELIX-3995] - Missing options in Bind annotation * [FELIX-4027] - The iPOJO Ant task requires org.objectweb.asm.tree * [FELIX-4046] - Inner class manipulation fails with expanded frames * [FELIX-4052] - Instance declaration not created correctly when using @Instantiate if the @Component specifies a name ** Improvement * [FELIX-3286] - Update POM to use the new parent * [FELIX-3452] - Extending maven-ipojo-plugin with directoryManipulation support. * [FELIX-3749] - Refactor the manipulator for better (and extensible) annotation support * [FELIX-3837] - PojoizationPlugin should be more extensible * [FELIX-3901] - Avoid converting Xml namespace declaration with @HandlerDeclaration * [FELIX-3927] - Exclude iPOJO 2.0 packages during manipulation ** New Feature * [FELIX-3699] - Allow annotations to handle custom component definitions. * [FELIX-4059] - Provide a CLI tool to manipulate iPOJO bundles ** Task * [FELIX-3903] - Migrate tests to pax exam 3 * [FELIX-3921] - Update pom to latest Felix's parent * [FELIX-3976] - Move the online manipulator out of the core bundle Changelog of the runtime project (1.10.0): ** Bug * [FELIX-3451] - "instance.name" attribute not recognized * [FELIX-3843] - ClassCastException when listing service properties of a non-ComponentFactory Factory service * [FELIX-3895] - iPOJO instance is not shown (with the "arch" commands) if constructor is failing * [FELIX-3896] - Null reference are injected with @Bind(optional=false) method on iPOJO components * [FELIX-3918] - iPOJO Logger cannot be dynamically configured on Equinox and KF * [FELIX-3919] - iPOJO Proxies strategy cannot be configured dynamically on Equinox and KF * [FELIX-3920] - Creation Strategy does not work on KF3 * [FELIX-3974] - Properties cannot be set as immutable using annotations * [FELIX-3995] - Missing options in Bind annotation * [FELIX-4041] - Properties starting with . should not be propagated * [FELIX-4048] - @Requires handler does not fail when no specification can be found * [FELIX-4053] - Avoid @StaticServiceProperty to be used on classes * [FELIX-4054] - Use current factory version to generate instance name if required ** Improvement * [FELIX-3860] - factories and instances iPOJO gogo commands should show the "public=false" instances/factories * [FELIX-3932] - Allow dependency filter's to get context-source variables * [FELIX-4040] - Implement config admin support to handle binding location properly * [FELIX-4045] - Chain Exceptions when possible ** New Feature * [FELIX-4034] - Instance configuration DSL ** Task * [FELIX-3892] - Upgrade runtime codebase to Java 5 * [FELIX-3903] - Migrate tests to pax exam 3 * [FELIX-3921] - Update pom to latest Felix's parent * [FELIX-3948] - Define a new extender model * [FELIX-3978] - Check that we don't use java 6+ API ** Wish * [FELIX-3926] - Provide metadata for the Extender namespace Changelog of the arch-gogo project (1.1.
[jira] [Updated] (FELIX-3879) [PATCH] overridable client scripts for the webconsole
[ https://issues.apache.org/jira/browse/FELIX-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-3879: - Fix Version/s: (was: webconsole-4.2.0) webconsole-4.2.2 Defering open issues to the next release. > [PATCH] overridable client scripts for the webconsole > - > > Key: FELIX-3879 > URL: https://issues.apache.org/jira/browse/FELIX-3879 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Bertrand Delacretaz >Priority: Minor > Fix For: webconsole-4.2.2 > > Attachments: FELIX-3879.patch > > > This patch adds an OverridableResourcesServlet to the webconsole, that > handles the /overridable path and returns an empty response for paths like > /system/console/overridable/scripts/* > If a Servlet service with a org.apache.felix.resources.servlet=true service > property is present, it is used to handle those requests instead. > This can be used to provide extension points in the webconsole where users > can replace default do-nothing scripts with their own variants. > I'ill provide another patch that uses this feature for progressive > enhancement of the console config page with help links. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 ] Felix Meschberger updated FELIX-3760: - Fix Version/s: (was: webconsole-4.2.0) webconsole-4.2.2 Defering open issues to the next 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 > Fix For: webconsole-4.2.2 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 ] Felix Meschberger updated FELIX-3614: - Fix Version/s: (was: webconsole-4.2.0) webconsole-4.2.2 Defering open issues to the next 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 > Fix For: webconsole-4.2.2 > > Attachments: webconsole_metatype_2.patch, webconsole_metatype.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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3880) [PATCH] placeholders for help links in the webconsole
[ https://issues.apache.org/jira/browse/FELIX-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-3880: - Fix Version/s: (was: webconsole-4.2.0) webconsole-4.2.2 Defering open issues to the next release. > [PATCH] placeholders for help links in the webconsole > - > > Key: FELIX-3880 > URL: https://issues.apache.org/jira/browse/FELIX-3880 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Bertrand Delacretaz >Priority: Minor > Fix For: webconsole-4.2.2 > > Attachments: FELIX-3880.patch, helplinks.jpg > > > The attached patch adds placeholders for help links to the webconsole, like >class="configHelpLink" > data-config-param="ds.loglevel" > data-config-pid="org.apache.felix.scr.ScrService" > data-config-name="SCR Log Level" > data-config-description="Allows limiting the amount..." > > > which can be enhanced with client-side javascript to build customized help > links. > The patch also adds a script reference at the end of the config page: >type="text/javascript" > src="/system/console/overridable/scripts/confighelp.js"> > which by default points to an empty script provided by the FELIX-3879 > mechanism, overridable by providing a Servlet service that returns the > desired code. > I have created an example such servlet/script at > https://github.com/bdelacretaz/felix-confighelp-demo, to test this feature: > -Apply the FELIX-3879 patch and this patch and install the patched webconsole > -Install the felix-confighelp-demo bundle > -The /system/console/overridable/scripts/confighelp.js path must then return > the felix-confighelp-demo's confighelp.js script > -Open a config form in the console, help links should be present next to each > parameter, which point to google.com for the demo -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3800) Support Category Translation
[ https://issues.apache.org/jira/browse/FELIX-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-3800: - Fix Version/s: (was: webconsole-4.2.0) webconsole-4.2.2 Defering open issues to the next release. > Support Category Translation > > > Key: FELIX-3800 > URL: https://issues.apache.org/jira/browse/FELIX-3800 > Project: Felix > Issue Type: Improvement > Components: Web Console >Reporter: Felix Meschberger > Fix For: webconsole-4.2.2 > > > FELIX-3769 added support to categorize the plugins to clean up the top > navigation and create menus. > The Category titles are not currently translated. It should be possible to > provide translations for those labels. Such translations should probably be > provided through the Web Console bundle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3848) Differentiate between unbound and new configuration
[ https://issues.apache.org/jira/browse/FELIX-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-3848: - Fix Version/s: (was: webconsole-4.2.0) webconsole-4.2.2 Defering open issues to the next release. > Differentiate between unbound and new configuration > --- > > Key: FELIX-3848 > URL: https://issues.apache.org/jira/browse/FELIX-3848 > Project: Felix > Issue Type: Improvement > Components: Web Console >Affects Versions: webconsole-4.0.0 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: webconsole-4.2.2 > > > The Configuration details display indicates the configuration binding of > configuration. If a configuration is not bound or does not exist yet (the GUI > is shown to create configuration), the location binding just indicates that > the configuration is unbound or new. > It would be good to have a better indication of whether a configuration is > actually new (to be created) or already exists but is just not bound/used yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-4065) Provide Gogo Shell integration for InventoryPrinter services
[ https://issues.apache.org/jira/browse/FELIX-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662989#comment-13662989 ] Carsten Ziegeler commented on FELIX-4065: - (a) I would go with "print" (b) both would be nice, but I don't think we need this for the first version (c) same as (b) > Provide Gogo Shell integration for InventoryPrinter services > > > Key: FELIX-4065 > URL: https://issues.apache.org/jira/browse/FELIX-4065 > Project: Felix > Issue Type: Bug > Components: Inventory >Affects Versions: inventory-1.0.0 >Reporter: Felix Meschberger > Attachments: gogo-shell-integration.patch > > > Apart from registering the InventoryPrinter services with the Apache Felix > Web Console, the printers should also be available through the Gogo Shell: > - Listing registered printers > - Calling printers > - Create ZIP file export from all (or select) printers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release of iPOJO Manipulator 1.10.0, iPOJO Runtime 1.10.0, iPOJO Gogo Command 1.1.0 and iPOJO's Web Console Plugin (1.7.0)
It took me a while but after realizing that we are only talking about 4 releases that each have several sub-projects that are not independently released but as part of their parent things started to make sense. I think we have to at one point get a better approach in place for doing our releases. Anyways, +1 I had to build the 4 releases with -DskipTest=true -Dinvoker.skip=true as otherwise, the integration tests did fail. I think you should either fix them or disable them on release. regards, Karl On Wed, May 15, 2013 at 11:41 PM, Guillaume Sauthier (OW2/GMail) < guillaume@gmail.com> wrote: > +1 (non binding) > > Thanks for cutting the release Clement > --G > > > 2013/5/15 Clement Escoffier > > > Hi, > > > > It's time to cut a release of the iPOJO manipulator (1.10.0), runtime > > project (1.10.0), Gogo's architecture command (1.1.0) and iPOJO Web > Console > > plugin (1.7.0). > > > > This releases contains: > > * bnd-ipojo-plugin - 1.10.0 > > * maven-ipojo-plugin - 1.10.0 > > * org.apache.felix.ipojo - 1.10.0 > > * org.apache.felix.ipojo.annotations - 1.10.0 > > * org.apache.felix.ipojo.ant - 1.10.0 > > * org.apache.felix.ipojo.api - 1.10.0 > > * org.apache.felix.ipojo.arch.gogo - 1.1.0 > > * org.apache.felix.ipojo.composite - 1.10.0 > > * org.apache.felix.ipojo.manipulator - 1.10.0 > > * org.apache.felix.ipojo.manipulator-project - 1.10.0 > > * org.apache.felix.ipojo.manipulator.online - 1.10.0 > > * org.apache.felix.ipojo.runtime-project - 1.10.0 > > * org.apache.felix.ipojo.webconsole - 1.7.0 > > > > Those releases contain a lot of bug fixes, improvements and new feature. > > The changelogs are below. > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachefelix-024/ > > > > 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 024 /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 (at least). > > > > Regards, > > > > Clement > > > > Changelog of the manipulator project (1.10.0): > > ** Bug > > * [FELIX-3827] - Error in bbd-ipojo-plugin of manipulating jar with > > embedded dependencies with maven bundle plugin + bnd-ipojo-plugin > > * [FELIX-3900] - @HandlerDeclaration do not convert DOM Attributes to > > iPOJO Attributes correctly > > * [FELIX-3938] - maven-ipojo-plugin does not behave as > bnd-ipojo-plugin > > * [FELIX-3974] - Properties cannot be set as immutable using > > annotations > > * [FELIX-3995] - Missing options in Bind annotation > > * [FELIX-4027] - The iPOJO Ant task requires org.objectweb.asm.tree > > * [FELIX-4046] - Inner class manipulation fails with expanded frames > > * [FELIX-4052] - Instance declaration not created correctly when > using > > @Instantiate if the @Component specifies a name > > > > ** Improvement > > * [FELIX-3286] - Update POM to use the new parent > > * [FELIX-3452] - Extending maven-ipojo-plugin with > > directoryManipulation support. > > * [FELIX-3749] - Refactor the manipulator for better (and extensible) > > annotation support > > * [FELIX-3837] - PojoizationPlugin should be more extensible > > * [FELIX-3901] - Avoid converting Xml namespace declaration with > > @HandlerDeclaration > > * [FELIX-3927] - Exclude iPOJO 2.0 packages during manipulation > > > > ** New Feature > > * [FELIX-3699] - Allow annotations to handle custom component > > definitions. > > * [FELIX-4059] - Provide a CLI tool to manipulate iPOJO bundles > > > > ** Task > > * [FELIX-3903] - Migrate tests to pax exam 3 > > * [FELIX-3921] - Update pom to latest Felix's parent > > * [FELIX-3976] - Move the online manipulator out of the core bundle > > > > Changelog of the runtime project (1.10.0): > > ** Bug > > * [FELIX-3451] - "instance.name" attribute not recognized > > * [FELIX-3843] - ClassCastException when listing service properties > of > > a non-ComponentFactory Factory service > > * [FELIX-3895] - iPOJO instance is not shown (with the "arch" > > commands) if constructor is failing > > * [FELIX-3896] - Null reference are injected with > > @Bind(optional=false) method on iPOJO components > > * [FELIX-3918] - iPOJO Logger cannot be dynamically configured on > > Equinox and KF > > * [FELIX-3919] - iPOJO Proxies strategy cannot be configured > > dynamically on Equinox and KF > > * [FELIX-3920] - Creation Strategy does not work on KF3 > > * [FELIX-3974] - Properties cannot be set as immutable using > > annotations > > * [FELIX-3995] - Missing options in Bind annotation > > * [FELIX-4041] - Properties starting with . should not be propagated > > * [FELIX-4048] - @Requires handler does not fail when no > specification > > can be
[jira] [Comment Edited] (FELIX-4065) Provide Gogo Shell integration for InventoryPrinter services
[ https://issues.apache.org/jira/browse/FELIX-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662942#comment-13662942 ] Felix Meschberger edited comment on FELIX-4065 at 5/21/13 12:46 PM: The patch provides two commands in the inventory scope: inventory:list -- list all registered InventoryPrinter services (includes the wrapped legacy ConfigurationPrinter services) inventory:show -- call the print method of a select printer by name Issues: (a) is "show" a good command name ? Or would "print" be better ? Or even something else ? (b) A single InventoryPrinter can currently only be called: (b1) Shold multiple be supported ? (b2) Should ZIP Attachments be available ? (c) How about a command to get all printers and attachements be written to a ZIP file ? was (Author: fmeschbe): Proposed patch > Provide Gogo Shell integration for InventoryPrinter services > > > Key: FELIX-4065 > URL: https://issues.apache.org/jira/browse/FELIX-4065 > Project: Felix > Issue Type: Bug > Components: Inventory >Affects Versions: inventory-1.0.0 >Reporter: Felix Meschberger > Attachments: gogo-shell-integration.patch > > > Apart from registering the InventoryPrinter services with the Apache Felix > Web Console, the printers should also be available through the Gogo Shell: > - Listing registered printers > - Calling printers > - Create ZIP file export from all (or select) printers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-4065) Provide Gogo Shell integration for InventoryPrinter services
[ https://issues.apache.org/jira/browse/FELIX-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-4065: - Attachment: gogo-shell-integration.patch Proposed patch > Provide Gogo Shell integration for InventoryPrinter services > > > Key: FELIX-4065 > URL: https://issues.apache.org/jira/browse/FELIX-4065 > Project: Felix > Issue Type: Bug > Components: Inventory >Affects Versions: inventory-1.0.0 >Reporter: Felix Meschberger > Attachments: gogo-shell-integration.patch > > > Apart from registering the InventoryPrinter services with the Apache Felix > Web Console, the printers should also be available through the Gogo Shell: > - Listing registered printers > - Calling printers > - Create ZIP file export from all (or select) printers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-4072) onGet and onSet methods do not provide the reference on the pojo object
[ https://issues.apache.org/jira/browse/FELIX-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier resolved FELIX-4072. -- Resolution: Fixed Fixed in trunk > onGet and onSet methods do not provide the reference on the pojo object > --- > > Key: FELIX-4072 > URL: https://issues.apache.org/jira/browse/FELIX-4072 > Project: Felix > Issue Type: Bug > Components: iPOJO >Affects Versions: ipojo-runtime-1.10 >Reporter: Clement Escoffier >Assignee: Clement Escoffier > Fix For: ipojo-runtime-1.10.1 > > > When the instance manager call the onGet and onSet methods on fields > interceptors, the pojo object parameter is set to `null`. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-4073) PrimitiveHandler.attach(ComponentInstance) is final
Guillaume Sauthier created FELIX-4073: - Summary: PrimitiveHandler.attach(ComponentInstance) is final Key: FELIX-4073 URL: https://issues.apache.org/jira/browse/FELIX-4073 Project: Felix Issue Type: Improvement Components: iPOJO Reporter: Guillaume Sauthier I would like to ease unit testing of Handlers. In my tests, I do not want to create a real InstanceManager, but I need early acces to it during the runtime (for encapsulation). I cannot access it directly easily soon enough because PrimitiveHandler.attach(ComponentInstance) is declared final. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
