[
https://issues.apache.org/jira/browse/FELIX-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Walid Joseph Gedeon updated FELIX-820:
--------------------------------------
Attachment: FELIX-820.patch
I've attached a patch for this issue, with the changes listed below.
It passed the following test cases:
1.a) bundle install, start [OK]
1.b) bundle stop, uninstall [OK]
2.a) host install, fragment install, host start [OK]
2.b) fragment start fails [OK]
2.c) fragment stop fails [OK]
2.d) fragment refresh, update [OK] [*]
2.e) fragment uninstall [OK]
2.f) fragment re-install [OK]
[*] fails as per FELIX-819 on shutdown
Summary of changes:
------------------------------
* [2008-11-19]
org.apache.felix.framework.searchpolicy.R4SearchPolicyCore#isFragment(IModule)
moved to
org.apache.felic.framework.util.Util and made public static. (FELIX-819)
* [2008-11-19]
org.apache.felic.framework.Felix#_startBundle(FelixBundle,boolean) and
#_stopBundle(FelixBundle,boolean) now checks if an attempt to start a
fragment is made
and throws a BundleException. #_updateBundle(FelixBundle,InputStream) and
#setFrameworkStartLevel(int)
will not call #stopBundle(FelixBundle,boolean) if the module is a fragment.
(FELIX-819)
> 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.
