[ 
https://issues.apache.org/jira/browse/ARIES-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401347#comment-13401347
 ] 

Mark Nuttall commented on ARIES-864:
------------------------------------

Hi John. In the AriesSubsystem constructor, 
'setSubsystemManifest(resource.getSubsystemManifest());' does what we'd expect, 
but then StartAction.run() includes 'SubsystemContentHeader header = 
subsystem.getSubsystemManifest().getSubsystemContentHeader();' - the 
subsystem's deployment manifest should take precedence, but it doesn't do so. 
Although I raised this JIRA specifically against Import-Package, there seems to 
be a general problem in that deployment.mf files are read, but then often 
languish unused. 
                
> Import-Package in deployment.mf is being ignored
> ------------------------------------------------
>
>                 Key: ARIES-864
>                 URL: https://issues.apache.org/jira/browse/ARIES-864
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>    Affects Versions: 1.0
>            Reporter: Mark Nuttall
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> When deploying an Application subsystem with a precalculated deployment.mf, 
> its Import-Package header is not taken into account. 
> The RawSubsystemResource constructor does not take the contents of 
> deployment.mf into account when calculating the subsystem's requirements. 
> Resulting calls to resource.getSubsystemManifest, such as from the 
> AriesSubsystem get an incorrect manifest as a result. 
> The OSGi V5 Enterprise spec, $134.15 states, "If available, the Sub-
> system service implementation must first attempt to use the Deployment 
> Manifest to deploy the Subsystem."
> ยง134.15.5 adds,
> "Any packages that match the Import-Package statement [in deployment.mf] must 
> be allowed into the Scoped Subsystem by its associated Region's sharing 
> policy."
> Regards, 
> Mark

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to