You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Norman Maurer <nm...@byteaction.de> on 2006/03/22 16:03:49 UTC
Re: DISCLAIMER about changes to MimeMessageWrapper (Was: svn
commit: r385090)
Hi,
any update on this ? Or will you send a email to the mailinglist when
the work is done ?
bye
Am Samstag, den 11.03.2006, 16:55 +0100 schrieb Stefano Bagnara:
> Please note that I wrote simple tests for this change but I still have
> not tested this version in real use cases.
>
> This patch and the upcoming "streaming support for db repositories"
> patch should be considered "critical" to James stability.
>
> So, please, don't deploy next nightly builds in production environments
> because this is not as much as tested as 2.3.0a1!
>
> I will run more real use tests at the end of this set of patches, but I
> wanted to commit this in steps to keep a better history of what I did.
>
> Another thing I would like to check out is wether we still need of the
> CopyOnWrite proxy after this patch or better we can get rid of it
> (eventually integrating some of the behaviour in the mimemessagewrapper).
>
> Stefano
>
> > Author: bago
> > Date: Sat Mar 11 07:19:33 2006
> > New Revision: 385090
> >
> > URL: http://svn.apache.org/viewcvs?rev=385090&view=rev
> > Log:
> > Removed wrapping from MimeMessageWrapper: now it is a simple MimeMessage extension (thanks to latest javamail providing much more protected methods than earlier releases)
> > Updated a few file/stream handling objects to use SharedFileInputStream so that javamail will not load the full message in memory when cloning the message. (Related to JAMES-134)
> > Added a bunch of tests to check consistency of the various MimeMessage implementation/constructors.
> > (Sorry, no "streaming support" for db repositories in this commit: still working on it)
> >
> > Added:
> > james/server/trunk/src/test/org/apache/james/core/MimeMessageFromMimeMessageTest.java
> > james/server/trunk/src/test/org/apache/james/core/MimeMessageFromSharedStreamTest.java
> > james/server/trunk/src/test/org/apache/james/core/MimeMessageFromStreamTest.java
> > james/server/trunk/src/test/org/apache/james/core/MimeMessageTest.java
> > james/server/trunk/src/test/org/apache/james/core/MimeMessageUtilTest.java
> > Modified:
> > james/server/trunk/src/java/org/apache/james/core/MimeMessageCopyOnWriteProxy.java
> > james/server/trunk/src/java/org/apache/james/core/MimeMessageInputStreamSource.java
> > james/server/trunk/src/java/org/apache/james/core/MimeMessageUtil.java
> > james/server/trunk/src/java/org/apache/james/core/MimeMessageWrapper.java
> > james/server/trunk/src/java/org/apache/james/mailrepository/filepair/AbstractFileRepository.java
> > james/server/trunk/src/java/org/apache/james/mailrepository/filepair/File_Persistent_Stream_Repository.java
> > james/server/trunk/src/java/org/apache/james/transport/mailets/AbstractRedirect.java
> > james/server/trunk/src/java/org/apache/james/transport/mailets/AddHeader.java
> > james/server/trunk/src/test/org/apache/james/core/MimeMessageCopyOnWriteProxyTest.java
> > james/server/trunk/src/test/org/apache/james/core/MimeMessageWrapperTest.java
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
Re: DISCLAIMER about changes to MimeMessageWrapper (Was: svn commit:
r385090)
Posted by Stefano Bagnara <ap...@bago.org>.
Norman Maurer wrote:
> Hi,
>
> any update on this ? Or will you send a email to the mailinglist when
> the work is done ?
I applied the patches to use streams writing to repositories.
Reading streams from db is what is taking me too much time and is not
ready to be committed.
I'm currently using the current trunk in a test server but it handle
only a few internal mails (less than 100 mails per day).
Stefano
> Am Samstag, den 11.03.2006, 16:55 +0100 schrieb Stefano Bagnara:
>> Please note that I wrote simple tests for this change but I still have
>> not tested this version in real use cases.
>>
>> This patch and the upcoming "streaming support for db repositories"
>> patch should be considered "critical" to James stability.
>>
>> So, please, don't deploy next nightly builds in production environments
>> because this is not as much as tested as 2.3.0a1!
>>
>> I will run more real use tests at the end of this set of patches, but I
>> wanted to commit this in steps to keep a better history of what I did.
>>
>> Another thing I would like to check out is wether we still need of the
>> CopyOnWrite proxy after this patch or better we can get rid of it
>> (eventually integrating some of the behaviour in the mimemessagewrapper).
>>
>> Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org