[
https://jira.nuxeo.com/browse/NXP-7784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Grisel resolved NXP-7784.
---------------------------------
Resolution: Fixed
Fix Version/s: 5.5
Component/s: Runtime
http://hg.nuxeo.org/nuxeo/nuxeo-runtime/rev/7b168ae9813b
> Invalid MANIFEST.MF file lead to nested NPEs that hide the root cause of the
> problem
> ------------------------------------------------------------------------------------
>
> Key: NXP-7784
> URL: https://jira.nuxeo.com/browse/NXP-7784
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Runtime
> Reporter: Olivier Grisel
> Assignee: Olivier Grisel
> Priority: Major
> Fix For: 5.5
>
>
> For instance if a Bundle MANIFEST.MF file has it's bundle symbolic name
> defined on the last line without a new line character it causes the
> BundleImpl.getActivator method to throw a NPE because the headers field is
> null which is in turn caught by a catch clauses in the start method only to
> trigger a second NPE for the same reason.
> The Runtime OSGi MANIFEST.MF handling logic should raise explicit
> BundleException when first encountering invalid manifest files rather than
> trying to ignore the issues and triggering undebuggable NullPointerExceptions
> later in the deployment process.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
