You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2013/05/21 14:47:16 UTC

[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