You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Alasdair Nottingham (JIRA)" <ji...@apache.org> on 2009/12/21 15:40:18 UTC
[jira] Resolved: (ARIES-52) Improved parsing of Application
metadata.
[ https://issues.apache.org/jira/browse/ARIES-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alasdair Nottingham resolved ARIES-52.
--------------------------------------
Resolution: Fixed
> Improved parsing of Application metadata.
> -----------------------------------------
>
> Key: ARIES-52
> URL: https://issues.apache.org/jira/browse/ARIES-52
> Project: Aries
> Issue Type: Improvement
> Components: Application
> Affects Versions: Incubation
> Reporter: Alasdair Nottingham
> Assignee: Alasdair Nottingham
> Fix For: Incubation
>
>
> The application.mf parsing support requires a java.util.jar.Manifest. This means that each line needs to be no more than 76 bytes long. This makes things harder for a developer. So I propose the following changes:
> 1. Add a new method to ManifestProcessor to do a friendly manifest parse
> 2. Remove the static ApplicationMetadataFactory as this is a non-optimal OSGi pattern
> 3. Add a new ApplicationMetadataManager service which is a service and will parse metadata from a Manifest, InputStream, and provide a mechanism for sharing parsed ApplicationMetadata when another client does not have access to the manifest.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.