[
https://issues.apache.org/jira/browse/ARIES-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401330#comment-13401330
]
John Ross commented on ARIES-864:
---------------------------------
You're correct. A deployment manifest should be taken as is. If the manifest is
present, the application should be deployed accordingly, and no further
computations should occur. Did you mean "resource.getDeploymentManifest" in
your write up, or are you saying there's also an issue with the subsystem
manifest?
> 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
