You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Jacques-Olivier Goussard (JIRA)" <ji...@apache.org> on 2009/04/01 02:03:50 UTC

[jira] Created: (FELIX-1018) ShellService not properly tracked

ShellService not properly tracked
---------------------------------

                 Key: FELIX-1018
                 URL: https://issues.apache.org/jira/browse/FELIX-1018
             Project: Felix
          Issue Type: Bug
          Components: Remote Shell
    Affects Versions: shell.remote-1.0.2
         Environment: JDK 6
            Reporter: Jacques-Olivier Goussard
            Priority: Minor


I start felix with:

felix.auto.start.1= \
 file:repository/org.apache.felix.shell-1.0.2.jar \
 file:repository/com.jog.felix.1.0.0.jar \

 file:repository/org.apache.felix.shell.tui-1.0.2.jar \
 file:repository/org.apache.felix.shell.remote-1.0.2.jar

I get:
Welcome to Felix.
=================
DEBUG: WIRE: 1.0 -> org.ungoverned.osgi.service.shell -> 1.0
DEBUG: WIRE: 1.0 -> org.osgi.service.startlevel -> 0
DEBUG: WIRE: 1.0 -> org.apache.felix.shell -> 1.0
DEBUG: WIRE: 1.0 -> org.osgi.framework -> 0
DEBUG: WIRE: 1.0 -> org.osgi.service.packageadmin -> 0
DEBUG: WIRE: 2.0 -> org.apache.felix.shell -> 1.0
DEBUG: WIRE: 2.0 -> org.osgi.framework -> 0
DEBUG: WIRE: 3.0 -> org.apache.felix.shell -> 1.0
DEBUG: WIRE: 3.0 -> org.osgi.framework -> 0
DEBUG: WIRE: 4.0 -> org.apache.felix.shell -> 1.0
DEBUG: WIRE: 4.0 -> org.osgi.framework -> 0
-> switch
Felix shell ?true
-> ps
START LEVEL 1
   ID   State         Level  Name
[   0] [Active     ] [    0] System Bundle (1.4.0)
[   1] [Active     ] [    1] Apache Felix Shell Service (1.0.2)
[   2] [Active     ] [    1] Jog Shell (1.0.0)
[   3] [Active     ] [    1] Apache Felix Shell TUI (1.0.2)
[   4] [Active     ] [    1] Apache Felix Remote Shell (1.0.2)
-> services 2

Jog Shell (2) provides:
-----------------------
->

So this states no services have been registered, though obviously shell TUI finds my ShellService instance as the
'switch' command shows.
-> services -u 3

Apache Felix Shell TUI (3) uses:
--------------------------------
->

So shell TUI doesn't seem to even use the service.

Looks like a bug in the 'services' command no 


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (FELIX-1018) ShellService not properly tracked

Posted by "Jacques-Olivier Goussard (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacques-Olivier Goussard updated FELIX-1018:
--------------------------------------------

    Attachment: MANIFEST.MF
                JogShell.java

Files to re-create the issue.

> ShellService not properly tracked
> ---------------------------------
>
>                 Key: FELIX-1018
>                 URL: https://issues.apache.org/jira/browse/FELIX-1018
>             Project: Felix
>          Issue Type: Bug
>          Components: Remote Shell
>    Affects Versions: shell.remote-1.0.2
>         Environment: JDK 6
>            Reporter: Jacques-Olivier Goussard
>            Priority: Minor
>         Attachments: JogShell.java, MANIFEST.MF
>
>
> I start felix with:
> felix.auto.start.1= \
>  file:repository/org.apache.felix.shell-1.0.2.jar \
>  file:repository/com.jog.felix.1.0.0.jar \
>  file:repository/org.apache.felix.shell.tui-1.0.2.jar \
>  file:repository/org.apache.felix.shell.remote-1.0.2.jar
> I get:
> Welcome to Felix.
> =================
> DEBUG: WIRE: 1.0 -> org.ungoverned.osgi.service.shell -> 1.0
> DEBUG: WIRE: 1.0 -> org.osgi.service.startlevel -> 0
> DEBUG: WIRE: 1.0 -> org.apache.felix.shell -> 1.0
> DEBUG: WIRE: 1.0 -> org.osgi.framework -> 0
> DEBUG: WIRE: 1.0 -> org.osgi.service.packageadmin -> 0
> DEBUG: WIRE: 2.0 -> org.apache.felix.shell -> 1.0
> DEBUG: WIRE: 2.0 -> org.osgi.framework -> 0
> DEBUG: WIRE: 3.0 -> org.apache.felix.shell -> 1.0
> DEBUG: WIRE: 3.0 -> org.osgi.framework -> 0
> DEBUG: WIRE: 4.0 -> org.apache.felix.shell -> 1.0
> DEBUG: WIRE: 4.0 -> org.osgi.framework -> 0
> -> switch
> Felix shell ?true
> -> ps
> START LEVEL 1
>    ID   State         Level  Name
> [   0] [Active     ] [    0] System Bundle (1.4.0)
> [   1] [Active     ] [    1] Apache Felix Shell Service (1.0.2)
> [   2] [Active     ] [    1] Jog Shell (1.0.0)
> [   3] [Active     ] [    1] Apache Felix Shell TUI (1.0.2)
> [   4] [Active     ] [    1] Apache Felix Remote Shell (1.0.2)
> -> services 2
> Jog Shell (2) provides:
> -----------------------
> ->
> So this states no services have been registered, though obviously shell TUI finds my ShellService instance as the
> 'switch' command shows.
> -> services -u 3
> Apache Felix Shell TUI (3) uses:
> --------------------------------
> ->
> So shell TUI doesn't seem to even use the service.
> Looks like a bug in the 'services' command no 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (FELIX-1018) ShellService not properly tracked

Posted by "Karl Pauls (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694335#action_12694335 ] 

Karl Pauls commented on FELIX-1018:
-----------------------------------

Ok, I see what is going on. 

Regarding shell.remote: I agree, it looks like it is not handling changing services correctly. 

Regarding the services command: Turns out that the services command filters out all services that are implementing Command. This is by design and not a bug (sorry for not thinking about that sooner). In case you want to see all your services you need to use the -a switch as in:

->  services -a

System Bundle (0) provides:
---------------------------
org.osgi.service.startlevel.StartLevel
org.osgi.service.packageadmin.PackageAdmin

Apache Felix Shell Service (1) provides:
----------------------------------------
org.apache.felix.shell.ShellService, org.ungoverned.osgi.service.shell.ShellService
org.apache.felix.shell.Command
org.apache.felix.shell.Command, org.apache.felix.shell.CdCommand
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command
org.apache.felix.shell.Command

Jog Shell (2) provides:
-----------------------
org.apache.felix.shell.ShellService, org.apache.felix.shell.Command

Apache Felix Bundle Repository (4) provides:
--------------------------------------------
org.osgi.service.obr.RepositoryAdmin
org.apache.felix.shell.Command

> ShellService not properly tracked
> ---------------------------------
>
>                 Key: FELIX-1018
>                 URL: https://issues.apache.org/jira/browse/FELIX-1018
>             Project: Felix
>          Issue Type: Bug
>          Components: Remote Shell
>    Affects Versions: shell.remote-1.0.2
>         Environment: JDK 6
>            Reporter: Jacques-Olivier Goussard
>            Priority: Minor
>         Attachments: JogShell.java, MANIFEST.MF
>
>
> I start felix with:
> felix.auto.start.1= \
>  file:repository/org.apache.felix.shell-1.0.2.jar \
>  file:repository/com.jog.felix.1.0.0.jar \
>  file:repository/org.apache.felix.shell.tui-1.0.2.jar \
>  file:repository/org.apache.felix.shell.remote-1.0.2.jar
> I get:
> Welcome to Felix.
> =================
> DEBUG: WIRE: 1.0 -> org.ungoverned.osgi.service.shell -> 1.0
> DEBUG: WIRE: 1.0 -> org.osgi.service.startlevel -> 0
> DEBUG: WIRE: 1.0 -> org.apache.felix.shell -> 1.0
> DEBUG: WIRE: 1.0 -> org.osgi.framework -> 0
> DEBUG: WIRE: 1.0 -> org.osgi.service.packageadmin -> 0
> DEBUG: WIRE: 2.0 -> org.apache.felix.shell -> 1.0
> DEBUG: WIRE: 2.0 -> org.osgi.framework -> 0
> DEBUG: WIRE: 3.0 -> org.apache.felix.shell -> 1.0
> DEBUG: WIRE: 3.0 -> org.osgi.framework -> 0
> DEBUG: WIRE: 4.0 -> org.apache.felix.shell -> 1.0
> DEBUG: WIRE: 4.0 -> org.osgi.framework -> 0
> -> switch
> Felix shell ?true
> -> ps
> START LEVEL 1
>    ID   State         Level  Name
> [   0] [Active     ] [    0] System Bundle (1.4.0)
> [   1] [Active     ] [    1] Apache Felix Shell Service (1.0.2)
> [   2] [Active     ] [    1] Jog Shell (1.0.0)
> [   3] [Active     ] [    1] Apache Felix Shell TUI (1.0.2)
> [   4] [Active     ] [    1] Apache Felix Remote Shell (1.0.2)
> -> services 2
> Jog Shell (2) provides:
> -----------------------
> ->
> So this states no services have been registered, though obviously shell TUI finds my ShellService instance as the
> 'switch' command shows.
> -> services -u 3
> Apache Felix Shell TUI (3) uses:
> --------------------------------
> ->
> So shell TUI doesn't seem to even use the service.
> Looks like a bug in the 'services' command no 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.