[jira] Commented: (FELIX-820) Throw an exception when starting a fragment bundle

["Walid Joseph Gedeon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648568#action_12648568 ] 

Walid Joseph Gedeon commented on FELIX-820:
-------------------------------------------

Which path would you chose to implement this? There are 2 main solutions I can propose:

1) With a Fragment Manager:
    - Add a Fragment Manager that would progressively hold the fragment related information
    - Move isFragment(), getPotentialHosts(), and a few other fragment specific code from R4SearchPolicyCore to the Fragment Manager
    * Add setIsFragment() and isFragment() to BundleInfo. It would be set on or around construction of a BundleImpl [ in installBundle(long,String, InputStream) ]
    * throw exceptions on attempt to start or stop

2) Without a Fragment Manager:
    - Make isFragment() in R4SearchPolicyCore public
    * Add setIsFragment() and isFragment() to BundleInfo. It would be set on or around construction of a BundleImpl [ in installBundle(long,String, InputStream) ]
    * throw exceptions on attempt to start or stop

Any thoughts?

> Throw an exception when starting a fragment bundle
> --------------------------------------------------
>
>                 Key: FELIX-820
>                 URL: https://issues.apache.org/jira/browse/FELIX-820
>             Project: Felix
>          Issue Type: Sub-task
>          Components: Framework, Specification compliance
>    Affects Versions: felix-1.4.0
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>             Fix For: felix-1.4.1
>
>
> The spec says attempts to start a fragment should result in an exception. Make it so.

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