You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/07/11 11:41:59 UTC

[jira] [Updated] (KARAF-555) shell command extensions updated to support iPOJO

     [ https://issues.apache.org/jira/browse/KARAF-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated KARAF-555:
---------------------------------------

    Fix Version/s: 3.1.0

> shell command extensions updated to support iPOJO
> -------------------------------------------------
>
>                 Key: KARAF-555
>                 URL: https://issues.apache.org/jira/browse/KARAF-555
>             Project: Karaf
>          Issue Type: Improvement
>          Components: console
>            Reporter: jamie campbell
>            Priority: Minor
>             Fix For: 3.1.0
>
>
> it would be good if karaf's blueprint based command integration supported iPOJO.  At the moment, if you have an iPOJO meta.xml creating an instance and automatically managing aggregated dependencies, it's off in a corner and ignored.  The blueprint stuff spawns its own instance.
> This integration could be as easy as adding a new attribute to the command's shell config xml so that in addition to specifying a class, you could also specify a specific instance that you'd like to have used.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira