[
https://issues.apache.org/jira/browse/HTTPCORE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Weber resolved HTTPCORE-120.
-----------------------------------
Resolution: Fixed
Done. I'm hacking faster than I'm thinking, so we have now two implementations
of the interface. The one in o.a.h.message is based on a Header[], typesafe and
doesn't support remove(). It's meant for use by applications, because it sure
isn't used by the framework. The second implementation is in o.a.h.util, based
on List, susceptible to ClassCastExceptions when used directly with a bad list,
supports remove() and is used by HeaderGroup, which in turn is used by
AbstractHttpMessage.
cheers,
Roland
> provide a HeaderIterator in HttpMessage
> ---------------------------------------
>
> Key: HTTPCORE-120
> URL: https://issues.apache.org/jira/browse/HTTPCORE-120
> Project: HttpComponents Core
> Issue Type: Sub-task
> Components: HttpCore
> Affects Versions: 4.0-alpha5
> Reporter: Roland Weber
> Assignee: Roland Weber
> Fix For: 4.0-alpha6
>
>
> Adding a HeaderIterator interface serves two purposes:
> 1. access to all headers of a given name without creating a temporary array
> 2. a home for iteration methods outside of java.util.Iterator, which is not
> part of J2ME
> See discussion on HTTPCORE-112 for details.
> cheers,
> Roland
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
