[jira] [Updated] (ARIES-958) BundleManifest.fromBundle(IFile) fails to parse OSGI headers when bundle manifest contains Name header.

["Timothy Ward (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARIES-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Ward updated ARIES-958:
-------------------------------

    Fix Version/s: util-1.1.1
    
> BundleManifest.fromBundle(IFile) fails to parse OSGI headers when bundle manifest contains Name header.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-958
>                 URL: https://issues.apache.org/jira/browse/ARIES-958
>             Project: Aries
>          Issue Type: Bug
>          Components: Util
>    Affects Versions: util-0.4
>            Reporter: Davy De Waele
>            Assignee: Timothy Ward
>             Fix For: util-1.1.1
>
>         Attachments: TestProject.zip
>
>
> When a bundle contains a Name header in its Manifest, the org.apache.aries.util.manifest.BundleManifest.fromBundle(IFile file) component starts parsing OSGI headers, but stops as soon as it encounters the "Name" header. If the "Name" header is placed before the "Bundle-SymbolicName" header, the bundle is considered invalid. 
> com.springsource.org.aspectj.weaver-1.6.5.RELEASE.jar is such a bundle (coming from the Spring enterprise bundle repository). It contains a Name header and when packaged inside an EBA fails to deploy on Websphere Liberty Profile due to the BundleManifest.fromBundle call. (some OSGI headers are skipped, including the Bundle-Symbolic name, leaving Aries to think this is an invalid bundle.) 
> Odly enough, When using BundleManifest.fromBundle(InputStream is), the problem does not occur, as different parsing logic is used.

--
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: http://www.atlassian.com/software/jira