Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Date: Tue, 6 Nov 2012 15:00:14 +0000 (UTC)
From: "Davy De Waele (JIRA)" <jira@apache.org>
To: dev@aries.apache.org
Message-ID: <1923170683.74490.1352214014265.JavaMail.jiratomcat@arcas>
In-Reply-To: <229538512.74482.1352213893176.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (ARIES-958) BundleManifest.fromBundle(IFile) fails
 to parse OSGI headers when bundle manifest contains Name header.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Davy De Waele updated ARIES-958:
--------------------------------

    Attachment: TestProject.zip

Added Testcase with 4 tests outlining the issue. (2 testcases with a bundle manifest containing a header using inputstream and IFile + 2 testcases with a budle manifest without a header using inputstream and IFile)
                
> 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
>         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.
> 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