You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Created) (JIRA)" <ji...@apache.org> on 2011/12/20 09:15:30 UTC

[jira] [Created] (SLING-2334) Register shell command through service factory

Register shell command through service factory
----------------------------------------------

                 Key: SLING-2334
                 URL: https://issues.apache.org/jira/browse/SLING-2334
             Project: Sling
          Issue Type: Improvement
          Components: Extensions
    Affects Versions: Extensions Thread Dumper 0.2.0
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: Extensions Thread Dumper 0.2.2


Currently the shell command is using an optional import, so when the shell bundle is not available on startup the command is never registered

We should rather use a dynamic import and a service factory to register the command. This should delay the class loading until the command is really used by the shell

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (SLING-2334) Register shell command through service factory

Posted by "Carsten Ziegeler (Closed) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-2334.
-----------------------------------

    
> Register shell command through service factory
> ----------------------------------------------
>
>                 Key: SLING-2334
>                 URL: https://issues.apache.org/jira/browse/SLING-2334
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Extensions Thread Dumper 0.2.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Extensions Thread Dumper 0.2.2
>
>
> Currently the shell command is using an optional import, so when the shell bundle is not available on startup the command is never registered
> We should rather use a dynamic import and a service factory to register the command. This should delay the class loading until the command is really used by the shell

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (SLING-2334) Register shell command through service factory

Posted by "Carsten Ziegeler (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-2334.
-------------------------------------

    Resolution: Fixed

Changed in revision 1221163
                
> Register shell command through service factory
> ----------------------------------------------
>
>                 Key: SLING-2334
>                 URL: https://issues.apache.org/jira/browse/SLING-2334
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Extensions Thread Dumper 0.2.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Extensions Thread Dumper 0.2.2
>
>
> Currently the shell command is using an optional import, so when the shell bundle is not available on startup the command is never registered
> We should rather use a dynamic import and a service factory to register the command. This should delay the class loading until the command is really used by the shell

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira