[
https://issues.apache.org/jira/browse/SLING-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783797#action_12783797
]
Justin Edelson commented on SLING-1210:
---------------------------------------
start() throws a BundleException which BootstrapInstaller catches and logs. So
it's not a severe problem, just an annoyance (and slightly inefficient to
create the BundleException instance).
Looking at PackageAdmin, the check should actually be:
return headerMap.contains(Constants.FRAGMENT_HOST);
> BootstrapInstaller will attempt (and fail) to start fragment bundles
> --------------------------------------------------------------------
>
> Key: SLING-1210
> URL: https://issues.apache.org/jira/browse/SLING-1210
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Affects Versions: Launchpad Base 2.1.0
> Reporter: Justin Edelson
>
> If you put a fragment bundle in the resource path scanned by
> BootstrapInstaller, it will attempt to start it, which fails because fragment
> bundles can't be started.
> I'll provide this as a proper patch soon. Here's an outline of the change:
> new method:
> private static boolean isFragment(Bundle bundle) {
> Dictionary headerMap = bundle.getHeaders();
> return headerMap.get(Constants.FRAGMENT_HOST) != null;
> }
> wrap bundle.start() with;
> if (!isFragment(bundle)) {
> bundle.start();
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
