Author: olegk
Date: Tue Feb 8 16:07:06 2011
New Revision: 1068460
URL: http://svn.apache.org/viewvc?rev=1068460&view=rev
Log:
Added #getDispositionType and #getFilename to the Entity interface
Modified:
james/mime4j/trunk/dom/src/main/java/org/apache/james/mime4j/dom/Entity.java
Modified:
Author: olegk
Date: Tue Feb 8 15:59:28 2011
New Revision: 1068457
URL: http://svn.apache.org/viewvc?rev=1068457&view=rev
Log:
Moved parser parameters to MimeBuilder and MessageBuilderImpl; removed
ParseParams
Removed:
james/mime4j/trunk/dom/src/main/java/org/apache/james/mime4j/dom/ParsePa
On Tue, 2011-02-08 at 11:58 +0100, Stefano Bagnara wrote:
> 2011/1/31 Oleg Kalnichevski :
...
> > In all honesty, I do not. I'll be more than happy to make ParseParams
> > non nullable, if that matters to you.
>
> I took some time to better think about it.
> I'm convinced that parse(InputStream,
[
https://issues.apache.org/jira/browse/MIME4J-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991991#comment-12991991
]
Oleg Kalnichevski commented on MIME4J-175:
--
Stefano
I personally find it unlikel
2011/1/31 Oleg Kalnichevski :
> On Mon, 2011-01-31 at 01:09 +0100, Stefano Bagnara wrote:
> ...
>> >> I don't find the new method parse(InputStream, ParseParams,
>> >> DecodeMonitor) very much appealing:
>> >> 1) it uses a configuration object (ParseParams) just to pass 2
>> >> booleans.. not a big
[
https://issues.apache.org/jira/browse/MIME4J-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991890#comment-12991890
]
Stefano Bagnara commented on MIME4J-175:
As you can see it was stuck with a propos
[
https://issues.apache.org/jira/browse/MIME4J-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved MIME4J-149.
Resolution: Fixed
The biggest issue was fixed. So let's mark it as resolved. We can file a
