You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "David Booz (JIRA)" <de...@tuscany.apache.org> on 2008/08/29 23:33:44 UTC

[jira] Commented: (TUSCANY-2566) OSGi NodeLauncher main does not start OSGi runtime

    [ https://issues.apache.org/jira/browse/TUSCANY-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627115#action_12627115 ] 

David Booz commented on TUSCANY-2566:
-------------------------------------

Looks like an attempt was made to integrate a fix, but it was done incorrectly.  The launcher instance cannot be created until AFTER OSGi is started.

> OSGi NodeLauncher main does not start OSGi runtime
> --------------------------------------------------
>
>                 Key: TUSCANY-2566
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2566
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA OSGi Integration
>    Affects Versions: Java-SCA-1.3
>         Environment: On revision 688186 of the trunk.
>            Reporter: David Booz
>            Assignee: Raymond Feng
>             Fix For: Java-SCA-Next
>
>         Attachments: node-launcher-osgi-2566.diff
>
>
> The main function in o.a.t.s.node.osgi.launcher.NodeLauncher does not start the OSGi runtime.  This was not caught because the JUnit testcases doesn't use this main to start the node.

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