[
https://issues.apache.org/jira/browse/ARIES-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679465#comment-13679465
]
John Ross commented on ARIES-1080:
----------------------------------
I don't believe there are classes for any of the human readable headers, and
there might be others. In general, header classes were added on an ad-hoc basis
when there appeared to be some value in drilling down into the value other than
separating out the parameters, which is done in AbstractHeader->GenericHeader.
I don't think that applies to the human readable headers. Any unrecognized
header (i.e. one without a corresponding class) will be turned into a
GenericHeader and should be available via Subsystem.getSubsystemHeaders().
It wouldn't hurt to have such a header but it would most likely be a no-op
extension of GenericHeader and not be particularly useful. I would be more
concerned if the header was not being parsed correctly or at all, but it
doesn't sound like that's the issue?
> Missing Description Header in Subsystem Manifest
> ------------------------------------------------
>
> Key: ARIES-1080
> URL: https://issues.apache.org/jira/browse/ARIES-1080
> Project: Aries
> Issue Type: Improvement
> Components: Subsystem
> Affects Versions: 1.0
> Reporter: Cristiano Gavião
> Priority: Critical
>
> Subsystem specs has a description header for the subsystem manifest.
> 134.2.1.8-
> Subsystem-Description:
> The Subsystem-Description header defines a human-readable description for
> this Subsystem, which can potentially be localized.
> org.apache.aries.subsystem.core.archive package doesn't contain a header
> class for it.
--
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
