aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Nuttall (JIRA)" <>
Subject [jira] [Resolved] (ARIES-969) Empty Bundle-Blueprint: header should result in no blueprint container
Date Tue, 18 Jun 2013 10:17:20 GMT


Mark Nuttall resolved ARIES-969.

    Resolution: Fixed
> Empty Bundle-Blueprint: header should result in no blueprint container
> ----------------------------------------------------------------------
>                 Key: ARIES-969
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: Application
>    Affects Versions: 0.4
>            Reporter: Mark Nuttall
>            Assignee: Mark Nuttall
>             Fix For: 0.4
>   Original Estimate: 2h
>  Remaining Estimate: 2h
> At the end of the OSGi R5 Enterprise spec section 121.3.4 we read, 
> "If the Bundle-Blueprint header is specified but empty, then the Blueprint bundle must
not be managed. This can be used to temporarily disable a Blueprint bundle."
> This behaviour is not currently implemented. As well as not being spec-compliant, it
can be time consuming to scan large bundles for blueprint files. I'll firstly use this defect
to change the behaviour so as to become spec-compliant. 
> One problem with the spec as written is that bundles that do not contain blueprint must
"opt out" of blueprint management by including an empty Bundle-Blueprint header. This is a
problem for users that consume third party bundles that are unwilling or unable to modify
their manifests. So I'm going to add a system property, "org.apache.aries.blueprint.header.mandatory".
Its default value will be "false". Setting it to 'true' will mean that bundles that do not
contain a Bundle-Blueprint: header in their manifests will not be scanned for blueprint and
will not get runtime blueprint containers. ModelledResourceManagerImpl.findBlueprints() is
expensive for large bundles, so this will yield substantial performance improvements for such

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message