Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <329339696.1227292304332.JavaMail.jira@brutus>
Date: Fri, 21 Nov 2008 10:31:44 -0800 (PST)
From: "Richard S. Hall (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Resolved: (FELIX-820) Throw an exception when starting a
 fragment bundle
In-Reply-To: <558658602.1226962784199.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Richard S. Hall resolved FELIX-820.
-----------------------------------

    Resolution: Fixed

I have applied a modified version of the patch; see the svn commit associated with this JIRA issue for the exact changes I made.

In short, I modified some of the comments to make them less precise, since it will be difficult to maintain this in the face of change spec section numbers, for example. I also modified some of the "if" conditions to check for ACTIVE state rather than fragments, since this might be more robust in the future if similar exceptions are introduced. Lastly, I thought of a special case that occurs in updateBundle(), where a previously ACTIVE non-fragment bundle is updated to be a fragment bundle. In that case, I mark its persistent state as inactive and log a warning.

Walid, please review and close if you are satisfied. Thanks!

> 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
>
>         Attachments: FELIX-820.patch
>
>
> 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.