mime4j/jspf and releasable artifacts/packages
I was just trying to fix maven bits for mime4j to place correct LICENSE/NOTICE files in the META-INF folder for the jar file and I had a doubt on what was the most useful release packages. After a few thoughts I end up with this choice: 1) binary jar => this is the "core" library. to be placed in the maven repository too. (e.g: james-mime4j-0.3.jar) 2) source jar => this is a jar useful for IDEs and contains all of the original and the *generated* java files. In particular in mime4j this contains also the files generated by javacc/jjtree because they may be useful while DEBUGGING in an IDE. This will end up in maven repository, too, and must contain the LICENSE/NOTICE files too. (e.g: james-mime4j-0.3-SNAPSHOT.jar) 3) "bin" package (zip + tar.gz): contains, inside a folder with the same name of the archive, the binary jar, the NOTICE/LICENSE files, and a lib folder including runtime dependencies for the library. (e.g: james-mime4j-0.3-bin.zip) 4) "project" package (zip + tar.gz): contains, inside a folder with the same name of the archive, the whole source tree checked out from the svn repository, including the "stage" folder and anything else we may have there. (e.g: james-mime4j-0.3-project.tar.gz) WDYT? I skipped "tar.bz" packaging by purpose: having zip and tar.gz is IMHO already redundant enough. Do we need any other packaging (or different) for library-products like mime4j/jsieve/jspf ? Maybe "src" is better than "project" as the classifier (postfix) the package #4 ? Stefano PS: download clicks from google analytics: # # Profile Name: james.apache.org # Date Range: 4/28/2007 - 5/4/2007 # 249 server/binaries/james-binary-2.3.1.zip 84 server/binaries/james-binary-2.3.1.tar.gz 45 server/binaries/james-2.3.0.zip 28 server/source/james-2.3.1-src.zip 20 server/source/james-2.3.1-src.tar.gz 13 server/binaries/james-MailetSDK-2.3.1.zip 12 server/source/james-with-phoenix-2.3.1-src.zip 9 server/binaries/james-2.3.0.tar.gz 4 server/source/james-2.3.0-src.zip 3 server/binaries/james-binary-2.3.1rc1.zip 3 server/source/james-with-phoenix-2.3.1-src.tar.gz 2 server/binaries/james-2.3.0.zip.asc 2 server/rc/binaries/james-binary-2.3.1.tar.gz 2 server/binaries/james-MailetSDK-2.3.1.tar.gz 1 server/rc/binaries/james-binary-2.3.1rc1.tar.gz 1 server/binaries/james-binary-2.3.1.zip.asc 1 server/binaries/james-binary-2.3.1.tar.gz.asc 1 jspf/beta/src/jspf-0.9b4-src.tar.bz2 1 jspf/beta/bin/jspf-0.9b4-bin.zip 1 server/source/james-with-phoenix-2.3.0-src.tar.gz Some consideration: 1) binary-vs-sources 10:1 2) signature checks 1/300 3) zip-vs-tgz 3:1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JCR back-end
Noel J. Bergman ha scritto: >>> I (or Jukka or I, depending on whom gets to what, when) are going to >>> rip out the JCR parts into standalone classes, and then have some >>> driver code for reading a message into the JCR, recreating the >>> message from the JCR, etc. Once that's all done, we'll start moving >>> it into JAMES, but we'll also want to preserve the ability for > >> I don't think we're going to make another JAMES subproject [for] >> the JCR backend. > > <> We might end up with just that. Apparently, there is a lot of > interest in storing e-mail in a JCR, and we are just (one of) the first to > give it a serious go in Open Source. For now, I'd prefer to work on it and > see what firms up. > > --- Noel Can you make a rationale about a standalone product regarding JCR and Mail but not involving JAMES Server ? What exactly should such a component to? Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jukka Zitting Committer Karma
Jukka Zitting ha scritto: > On 5/4/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: >> *My* *preference* is still to have it in "server/sandbox" as this JCR >> stuff is related to JAMES Server as I don't think we're going to make >> another JAMES subproject (at the same level of postage, mailet api, >> jspf, mime4j, jsieve, server) for the JCR backend. > > I moved the component now (revision 535391) to server/sandbox. > > BR, > > Jukka Zitting Thank you very much :-) Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Resolved: (MAILET-1) Fix commit messages to go to mailet-api@
Thx Dude :-) On 5/4/07, Noel J. Bergman (JIRA) wrote: [ https://issues.apache.org/jira/browse/MAILET-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noel J. Bergman resolved MAILET-1. -- Resolution: Fixed Should be fixed. > Fix commit messages to go to mailet-api@ > > > Key: MAILET-1 > URL: https://issues.apache.org/jira/browse/MAILET-1 > Project: Mailet API > Issue Type: Task > Environment: SVN >Reporter: Danny Angus > Assigned To: Noel J. Bergman > > commits to james/mailet/ currently go to server-dev@ -- 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]
Re: [EMAIL PROTECTED]: Project james-server (in module james-server) failed
This is my bad. Stefan spoke to me about it, I need to set up mailet with a Gump descriptor. I'll get round to it in the next week or two, being honest about my time, Noel & I agree that it isn't critical because the only downstream dependence is server. Shout if you disagree. d. On 5/4/07, Gump wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project james-server has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - james-server : James Server Full details are available at: http://vmgump.apache.org/gump/public/james-server/james-server/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [james-server-core-library-03052007.jar] identifier set to project name -DEBUG- Dependency on javamail exists, no need to add for property gump.resource.javamail. -DEBUG- Dependency on magic exists, no need to add for property magic.home. -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/james-server/james-server/gump_work/build_james-server_james-server.html Work Name: build_james-server_james-server (Type: Build) Work ended in a state of : Failed Elapsed: 15 secs Command Line: /opt/jdk1.5/bin/java -Djava.awt.headless=true org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dgump.resource.dnsjava=/usr/local/gump/public/workspace/james-server/stage/dnsjava/jars/dnsjava-2.0.3.jar -Dgump.resource.javamail=/usr/local/gump/packages/javamail-1.4/mail.jar -Dgump.resource.jce=/usr/local/gump/packages/jce/jce-jdk13-116.jar -Dmagic.home=/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/03052007 -Dgump.resource.geronimo-spec-jms=/usr/local/gump/packages/jms1.1/lib/jms.jar -Dgump.resource.cornerstone-scheduler-api=/usr/local/gump/public/workspace/excalibur/cornerstone/scheduler/api/target/excalibur-cornerstone-scheduler-api-03052007.jar -Dgump.resource.commons-logging=/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-03052007.jar -Dgump.resource.excalibur-pool-impl=/usr/local/gump/public/workspace/excalibur/components/pool/impl/target/excalibur-pool-impl-03052007.jar -Dgump.resource.cornerstone-threads-api=/usr/local/gump/public/workspace/excalibur/cornerstone/threads/api/target/excalibur-cornerstone-threads-api-03052007.jar -Dgump.resource.avalon-framework-api=/usr/local/gump/public/workspace/excalibur/framework/api/target/excalibur-framework-api-03052007.jar -Dgump.resource.avalon-logkit=/usr/local/gump/public/workspace/excalibur/containerkit/logkit/target/excalibur-logkit-03052007.jar -Dgump.resource.cornerstone-connection-impl=/usr/local/gump/public/workspace/excalibur/cornerstone/connection/impl/target/excalibur-cornerstone-connection-impl-03052007.jar -Dversion=03052007 -Dgump.resource.cornerstone-datasources-api=/usr/local/gump/public/workspace/excalibur/cornerstone/datasources/api/target/excalibur-cornerstone-datasources-api-03052007.jar -Dgump.resource.cornerstone-store-api=/usr/local/gump/public/workspace/excalibur/cornerstone/store/api/target/excalibur-cornerstone-store-api-03052007.jar -Dbuild.sysclasspath=last -Dgump.resource.log4j=/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-03052007.jar -Dgump.resource.cornerstone-connection-api=/usr/local/gump/public/workspace/excalibur/cornerstone/connection/api/target/excalibur-cornerstone-connection-api-03052007.jar -Dgump.resource.commons-net=/usr/local/gump/public/workspace/jakarta-commons/net/dist/commons-net-03052007.jar -Dgump.resource.commons-pool=/usr/local/gump/public/workspace/jakarta-commons/pool/dist/commons-pool.jar -Dgump.resource.bcmail=/usr/local/gump/packages/bouncycastle-jdk14/bcmail-130.jar -Dgump.signature=03052007 -Dgump.resource.commons-dbcp=/usr/local/gump/public/workspace/jakarta-commons/dbcp/dist/commons-dbcp.jar -Dgump.resource.mailapi=/usr/local/gump/packages/javamail-1.4/mail.jar -Dgump.resource.excalibur-pool-api=/usr/local/gump/public/workspace/excalibur/components/pool/api/target/excalibur-pool-api-03052007.jar -Dgump.resource.excalibur-thread-api=/usr/local/gump/public/workspace/excalibur/components/thread/api/target/excalibur-thread-api-03052007.jar -Dgump.resource.bcprov=/usr/local/gump/packages/bouncycastle-jdk14/bcprov-130.jar -Dgump.resource.cornerstone-sockets-api=/usr/local/gump/public/workspace/excalibur/cornerstone/sockets/api/target/excalibur-cornerstone-sockets-api-03052007.jar -Dgump.resource.cornerstone-threads-impl=/usr/
Re: i am not getting subject content in utf-8 format
it might help us to help you if you can attach a UTF8 encoded copy of the raw message - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jukka Zitting Committer Karma
On 5/4/07, Jukka Zitting <[EMAIL PROTECTED]> wrote: I moved the component now (revision 535391) to server/sandbox. ... and now we have you on the hook! ;-) Welcome! d. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAMES Talk
Norman (thanks Noel, for the nice comment) I got some good feedback, people who felt that the talk really revealed what James can do in a way that our other resources can't. I did a demo where I created a mailet (to add a subject prefix) and configure a newly downloaded instance with it in two minutes flat, and that impressed one or two. I'll feed back more of the more complicated stuff once the dust settles, I've just got home. Thanks for asking :-) d. On 5/5/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote: Danny's talk was excellent, what I got to see of it before I had to leave for a conference call. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JCR back-end
> > I (or Jukka or I, depending on whom gets to what, when) are going to > > rip out the JCR parts into standalone classes, and then have some > > driver code for reading a message into the JCR, recreating the > > message from the JCR, etc. Once that's all done, we'll start moving > > it into JAMES, but we'll also want to preserve the ability for > I don't think we're going to make another JAMES subproject [for] > the JCR backend. <> We might end up with just that. Apparently, there is a lot of interest in storing e-mail in a JCR, and we are just (one of) the first to give it a serious go in Open Source. For now, I'd prefer to work on it and see what firms up. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JAMES Talk
Danny's talk was excellent, what I got to see of it before I had to leave for a conference call. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jukka Zitting Committer Karma
Hi, On 5/4/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: Noel J. Bergman ha scritto: > Stefano Bagnara wrote: >> Jukka Zitting ha scritto: >>> The prototype JCR store mailet we did during the ApacheCon is now in >>> james/sandbox/james-jcr (see revision 535260). It's very simple for >>> now, but I'll be working on the prototype during the next few weeks. > >> Maybe "/james/server/sandbox/" was better that "/james/sandbox/" as it >> is specific to the Server product: can we move it? [...] *My* *preference* is still to have it in "server/sandbox" as this JCR stuff is related to JAMES Server as I don't think we're going to make another JAMES subproject (at the same level of postage, mailet api, jspf, mime4j, jsieve, server) for the JCR backend. I moved the component now (revision 535391) to server/sandbox. BR, Jukka Zitting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r535391 - in /james: sandbox/james-jcr/ server/sandbox/james-jcr/
Author: jukka Date: Fri May 4 14:59:56 2007 New Revision: 535391 URL: http://svn.apache.org/viewvc?view=rev&rev=535391 Log: sandbox/james-jcr: Moved the JCR prototype to server/sandbox Added: james/server/sandbox/james-jcr/ - copied from r535390, james/sandbox/james-jcr/ Removed: james/sandbox/james-jcr/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: i am not getting subject content in utf-8 format
[EMAIL PROTECTED] wrote: > On 5/4/07, ketanbparekh <[EMAIL PROTECTED]> wrote: > > > I am trying to filter mails by passing persian words in > subject. But persian > > words appear as ? marks in subject and jsieve is not able > to filter it. > > This is a complex area, and it really depends where the > corruption is occuring. > You need to ensure that the software which creates the message, your > sieve scripts, and the software you use to view it all are using > UTF-8. > > Then if there is still a problem we need to make sure that the charset > is properly recorded in the headers, and that the header is escaped > correctly using base64 or Uuencode. All of the above is true. I suspect that the problem is not within jSieve. This can be proven by removing it from the chain and seeing if retrieved mails "persian words [still] appear as ? marks in subject". For information, here is how RFC 3028 says jSieve should work with regard to character sets... --- 2.1. Form of the Language The language consists of a set of commands. Each command consists of a set of tokens delimited by whitespace. The command identifier is the first token and it is followed by zero or more argument tokens. Arguments may be literal data, tags, blocks of commands, or test commands. The language is represented in UTF-8, as specified in [UTF-8]. Tokens in the ASCII range are considered case-insensitive. 2.7.2. Comparisons Across Character Sets All Sieve scripts are represented in UTF-8, but messages may involve a number of character sets. In order for comparisons to work across character sets, implementations SHOULD implement the following behavior: Implementations decode header charsets to UTF-8. Two strings are considered equal if their UTF-8 representations are identical. Implementations should decode charsets represented in the forms specified by [MIME] for both message headers and bodies. Implementations must be capable of decoding US-ASCII, ISO-8859-1, the ASCII subset of ISO-8859-* character sets, and UTF-8. If implementations fail to support the above behavior, they MUST conform to the following: No two strings can be considered equal if one contains octets greater than 127. --- ...if it doesn't, let us know! Cheers -- Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JAMES Talk
Hi Danny, how was the JAMES talk ? Many intressted people there? Any matrial you want to make public for us ? bye Norman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (MIME4J-12) WriteTo closes the outputstream too early (java.io.IOException: Bad file descriptor error)
[
https://issues.apache.org/jira/browse/MIME4J-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Norman Maurer resolved MIME4J-12.
-
Resolution: Fixed
Assignee: Norman Maurer
Remove the close
> WriteTo closes the outputstream too early (java.io.IOException: Bad file
> descriptor error)
> --
>
> Key: MIME4J-12
> URL: https://issues.apache.org/jira/browse/MIME4J-12
> Project: Mime4j
> Issue Type: Bug
>Affects Versions: 0.3
>Reporter: Stefano Bagnara
> Assigned To: Norman Maurer
> Fix For: 0.3
>
>
> On server-dev, GX GLIX reported this:
> ---
> Hi all
> I sincerely apologise for the delay, I have had other priorities and had to
> put this aside till now, after futher debugging I have come across the cause
> of the java.io.IOException: Bad file descriptor error.
> In the file /org/mime4j/message/Header.java the following code is found
> public void writeTo(OutputStream out) throws IOException {
> String charString = ((ContentTypeField)
> getField(Field.CONTENT_TYPE)).getCharset();
> BufferedWriter writer = new BufferedWriter(new OutputStreamWriter(out,
> CharsetUtil.getCharset(charString)),8192);
> writer.write(toString()+ "\r\n");
> writer.flush();
> writer.close();
> }
> as you can see the output stream is closed here.
> This is cause of the IOException as the stream is used later again for
> writing.
> I tried commenting the writer.close(); call and it worked fine, however I
> dont know what the implications of this may be.
> The case I am facing is a multipart message which calls the writeTo method
> below
> public void writeTo(OutputStream out) throws IOException {
> getHeader().writeTo(out);
> Body body = getBody();
> if (body instanceof Multipart) {
> Multipart mp = (Multipart) body;
> mp.writeTo(out);
> } else {
> body.writeTo(out);
> }
> }
> when getHeader().writeTo(out); is called the stream is closed and when
> mp.writeTo(out); is called the exception is throw as the stream is
> closed.Regards
--
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]
svn commit: r535332 - /james/mime4j/trunk/src/main/java/org/apache/james/mime4j/message/Header.java
Author: norman Date: Fri May 4 10:32:06 2007 New Revision: 535332 URL: http://svn.apache.org/viewvc?view=rev&rev=535332 Log: Remove the close of the given OutputStream (was done by mistake). See MIME4J-12 (Thx to GX for reporting) Modified: james/mime4j/trunk/src/main/java/org/apache/james/mime4j/message/Header.java Modified: james/mime4j/trunk/src/main/java/org/apache/james/mime4j/message/Header.java URL: http://svn.apache.org/viewvc/james/mime4j/trunk/src/main/java/org/apache/james/mime4j/message/Header.java?view=diff&rev=535332&r1=535331&r2=535332 == --- james/mime4j/trunk/src/main/java/org/apache/james/mime4j/message/Header.java (original) +++ james/mime4j/trunk/src/main/java/org/apache/james/mime4j/message/Header.java Fri May 4 10:32:06 2007 @@ -150,7 +150,6 @@ BufferedWriter writer = new BufferedWriter(new OutputStreamWriter(out, CharsetUtil.getCharset(charString)),8192); writer.write(toString()+ "\r\n"); writer.flush(); -writer.close(); } } - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [mime4j] null charset error
Hi,
thx for looking deeper at it. I will commit the fix soon :-)
bye
Norman
GX GLIX schrieb:
> Hi Stefano
>
> Sorry about that.. I made the mistake of switching to windows live
> (beta) and it screwed thing up..
> hope this is clearer
>
> GX
>
>> From: Stefano Bagnara <[EMAIL PROTECTED]>
>> Reply-To: "James Developers List"
>> To: James Developers List
>> Subject: Re: [mime4j] null charset error
>> Date: Fri, 04 May 2007 11:19:36 +0200
>>
>> This message come through totally unformatted.
>> I formatted it and opened a JIRA issue [1] so we can track it.
>>
>> Thank you,
>> Stefano
>>
>> [1] http://issues.apache.org/jira/browse/MIME4J-12
>>
>> GX GLIX ha scritto:
>> >
> Hi all
>
> I sincerely apologise for the delay, I have had other priorities and
> had to put this aside till now, after futher debugging I have come
> across the cause of the java.io.IOException: Bad file descriptor error.
>
> In the file /org/mime4j/message/Header.java the following code is found
>
> public void writeTo(OutputStream out) throws IOException {
>String charString = ((ContentTypeField)
> getField(Field.CONTENT_TYPE)).getCharset();
>
>BufferedWriter writer = new BufferedWriter(new
> OutputStreamWriter(out, CharsetUtil.getCharset(charString)),8192);
>writer.write(toString()+ "\r\n");
>writer.flush();
>writer.close();
>}
>
> as you can see the output stream is closed here. This is cause of the
> IOException as the stream is used later again for writing.
> I tried commenting the writer.close(); call and it worked fine,
> however I dont know what the implications of this may be.
>
> The case I am facing is a multipart message which calls the writeTo
> method below
>
>public void writeTo(OutputStream out) throws IOException {
>getHeader().writeTo(out);
>
>Body body = getBody();
>if (body instanceof Multipart) {
>Multipart mp = (Multipart) body;
>mp.writeTo(out);
>} else {
>body.writeTo(out);
>}
>}
>
> when getHeader().writeTo(out); is called the stream is closed and when
> mp.writeTo(out); is called the exception is throw as the stream is
> closed.
>
> Regards
> GX
>
>
>> >From: Norman Maurer <[EMAIL PROTECTED]>> >Reply-To: "Jam
>> es Developers List" > >To: James
>> Developers List > >Subject: Re: [mime4j]
>> null charset error> >Date: Tue, 24 Apr 2007 15:36:34 +0200> >> >Hi
>> GX,> >> >what JDK and OS you using? I found some intressting stuff:>
>> >> >http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322678>
>> >http://256.com/gray/docs/misc/java_bad_file_descriptor_close_bug.shtml>
>> >> >bye> >Norman> >> >> >GX GLIX schrieb:> > > Hi All> > >> > > I am
>> getting a "Null charset name" error during parsing, it seems that> >
>> > getCharset(String charsetName) is passed an empty string... I
>> tried> > > the following hack to fix it:> > >> > > ..> > >
>> public static java.nio.charset.Charset getCharset(String> > >
>> charsetName) {> > >if(charsetName == null)> > >
>> charsetName = "ISO8859-1";> > >java.nio.charset.Charset c =>
>> > > java.nio.charset.Charset.forName(charsetName);> > > >
>> > >> > > now the result is :> > >> > > java.i
>> o.IOException: Bad file descriptor> > > at
>> java.io.FileOutputStream.writeBytes(Native Method)> > > at
>> java.io.FileOutputStream.write(FileOutputStream.java:260)> > >
>> at> > >
>> sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)>
>> > > at> > > >
>> >sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)>
>> > >> > > at> > >
>> sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)>
>> > > at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)> >
>> > at
>> java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)> >
>> > at java.io.BufferedWriter.flush(BufferedWriter.java:230)> >
>> > at org.mime4j.message.Header.writeTo(Header.java:152)> > >
>> at org.mime4j.message.BodyPart.writeTo(BodyPart.java:39)> > > at
>> org.mime4j.message.Multipart.writeTo(Multipart.java:178)> > > at
>> org.mime4j.message.Message.writeTo(Message.java:91)> > > any ideas
>> anyone?> > >> > > ___
>> __> > > FREE pop-up blocking with the new MSN Toolbar
>> - get it now!> > >
>> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/> > >> >
>> >> > >
>> ->
>> > > To unsubscribe, e-mail: [EMAIL PROTECTED]>
>> > > For additional commands, e-mail:
>> [EMAIL PROTECTED]> > >> > >> > > > > >> > >> >> >>
>> >->
>> >To unsubscribe, e-mail: [EMAIL PROTECTED]>
>> >For additional commands, e-mail: [EMAIL PROTECTED]>
>> >> >
>> _>
>> Express yourself instantly with MSN Messenger! Dow
Re: Jukka Zitting Committer Karma
Noel J. Bergman ha scritto: > Stefano Bagnara wrote: > >> Jukka Zitting ha scritto: >>> The prototype JCR store mailet we did during the ApacheCon is now in >>> james/sandbox/james-jcr (see revision 535260). It's very simple for >>> now, but I'll be working on the prototype during the next few weeks. > >> Maybe "/james/server/sandbox/" was better that "/james/sandbox/" as it >> is specific to the Server product: can we move it? > > I can, but although it currently has a mailet in it, I (or Jukka or I, > depending on whom gets to what, when) are going to rip out the JCR parts into > standalone classes, and then have some driver code for reading a message into > the JCR, recreating the message from the JCR, etc. Once that's all done, > we'll start moving it into JAMES, but we'll also want to preserve the ability > for standalone code. > > So I don't recall care about where it is too much now. Well, we have a STATUS file that should be moved back to server trunk (after Robert refactored into modules it has been misplaced): http://svn.apache.org/repos/asf/james/server/trunk/phoenix-deployment/STATUS It should be updated to reference the jcr sandbox goal, status, owner (weird word, but let's say it is the list of the most active committers for that sandbox). *My* *preference* is still to have it in "server/sandbox" as this JCR stuff is related to JAMES Server as I don't think we're going to make another JAMES subproject (at the same level of postage, mailet api, jspf, mime4j, jsieve, server) for the JCR backend. Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jukka Zitting Committer Karma
Stefano Bagnara wrote: > Jukka Zitting ha scritto: > > The prototype JCR store mailet we did during the ApacheCon is now in > > james/sandbox/james-jcr (see revision 535260). It's very simple for > > now, but I'll be working on the prototype during the next few weeks. > Maybe "/james/server/sandbox/" was better that "/james/sandbox/" as it > is specific to the Server product: can we move it? I can, but although it currently has a mailet in it, I (or Jukka or I, depending on whom gets to what, when) are going to rip out the JCR parts into standalone classes, and then have some driver code for reading a message into the JCR, recreating the message from the JCR, etc. Once that's all done, we'll start moving it into JAMES, but we'll also want to preserve the ability for standalone code. So I don't recall care about where it is too much now. > And maybe we are missing svn notifications for the /james/sandbox > folder: Noel, can you fix it so the next time we don't miss a commit? :-) As you later noticed, we're already fine. It was just pending moderation. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JAMES Server Nightly Build Report
Stefano Bagnara wrote: > Noel J. Bergman ha scritto: >> it doesn't remove files from the staging area, so an old copy >> could still be used if not overwritten > I think you're missing something because here is not happening > what you say (I use "clean" before the dist): ant exited with > error. You may be right. I'll look further. The network here is unstable, and I'm just happy that I could even reach the build server. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jukka Zitting Committer Karma
Stefano Bagnara ha scritto: > And maybe we are missing svn notifications for the /james/sandbox > folder: Noel, can you fix it so the next time we don't miss a commit? I was wrong! The notification message was in the moderation queue: I just "allowed" jukka at apache to send messages to server-dev ;-) Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r535260 - in /james/sandbox/james-jcr: ./ src/ src/main/ src/main/java/ src/main/java/org/ src/main/java/org/apache/ src/main/java/org/apache/james/ src/main/java/org/apache/james/jcr/
Author: jukka Date: Fri May 4 07:37:14 2007 New Revision: 535260 URL: http://svn.apache.org/viewvc?view=rev&rev=535260 Log: sandbox/james-jcr: The prototype JCR store mailet Added: james/sandbox/james-jcr/ james/sandbox/james-jcr/LICENSE.txt (with props) james/sandbox/james-jcr/NOTICE.txt (with props) james/sandbox/james-jcr/README.txt (with props) james/sandbox/james-jcr/pom.xml (with props) james/sandbox/james-jcr/src/ james/sandbox/james-jcr/src/main/ james/sandbox/james-jcr/src/main/java/ james/sandbox/james-jcr/src/main/java/org/ james/sandbox/james-jcr/src/main/java/org/apache/ james/sandbox/james-jcr/src/main/java/org/apache/james/ james/sandbox/james-jcr/src/main/java/org/apache/james/jcr/ james/sandbox/james-jcr/src/main/java/org/apache/james/jcr/JCRStoreMailet.java (with props) Added: james/sandbox/james-jcr/LICENSE.txt URL: http://svn.apache.org/viewvc/james/sandbox/james-jcr/LICENSE.txt?view=auto&rev=535260 == --- james/sandbox/james-jcr/LICENSE.txt (added) +++ james/sandbox/james-jcr/LICENSE.txt Fri May 4 07:37:14 2007 @@ -0,0 +1,218 @@ + Apache License + Version 2.0, January 2004 +http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable +
Re: Jukka Zitting Committer Karma
Jukka Zitting ha scritto: > The prototype JCR store mailet we did during the ApacheCon is now in > james/sandbox/james-jcr (see revision 535260). It's very simple for > now, but I'll be working on the prototype during the next few weeks. > > BR, > > Jukka Zitting Cool! I will look at it for sure! Maybe "/james/server/sandbox/" was better that "/james/sandbox/" as it is specific to the Server product: can we move it? And maybe we are missing svn notifications for the /james/sandbox folder: Noel, can you fix it so the next time we don't miss a commit? Thank you, Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAMES Server Nightly Build Report
Noel J. Bergman ha scritto: >> If you prefer to clean the build.xml instead of changing your build >> server I have no problem with this. > > We'd already determined that a dist should imply a full clean. The old > build.xml did this, but that was lost in the refactoring. I've made the > change, but it is insufficient, because it doesn't remove files from the > staging area, so an old copy could still be used if not overwritten (which > is what happened when the mailet API was removed). > > --- Noel I think you're missing something because here is not happening what you say (I use "clean" before the dist): ant exited with error. And you may have noticed that also gump failed. Thank you for the fix, Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jukka Zitting Committer Karma
Hi, On 5/4/07, Serge Knystautas <[EMAIL PROTECTED]> wrote: On 5/2/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > Jukka Zitting, JackRabbit Committer & PMC Chair, has volunteered to help > work on a Proof of Concept related to the use of JCR as our unified data > store. The proof of concept will start by focusing on the modelling of the > data in JCR, and will build from the JCR side out, not start with existing > JAMES code at all. Commit privs granted to Jukka. Thanks! The prototype JCR store mailet we did during the ApacheCon is now in james/sandbox/james-jcr (see revision 535260). It's very simple for now, but I'll be working on the prototype during the next few weeks. BR, Jukka Zitting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JAMES Server Nightly Build Report
> If you prefer to clean the build.xml instead of changing your build > server I have no problem with this. We'd already determined that a dist should imply a full clean. The old build.xml did this, but that was lost in the refactoring. I've made the change, but it is insufficient, because it doesn't remove files from the staging area, so an old copy could still be used if not overwritten (which is what happened when the mailet API was removed). --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r535255 - /james/server/trunk/build.xml
Author: noel Date: Fri May 4 07:28:48 2007 New Revision: 535255 URL: http://svn.apache.org/viewvc?view=rev&rev=535255 Log: dist build should be done after a clean Modified: james/server/trunk/build.xml Modified: james/server/trunk/build.xml URL: http://svn.apache.org/viewvc/james/server/trunk/build.xml?view=diff&rev=535255&r1=535254&r2=535255 == --- james/server/trunk/build.xml (original) +++ james/server/trunk/build.xml Fri May 4 07:28:48 2007 @@ -132,7 +132,7 @@ +depends='clean'> Building modules, performing standard deployments and creating standard distributions - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAMES Server Nightly Build Report
Noel J. Bergman ha scritto: >> What target is/are invoked by the build server? > > ant dist, since clean is supposed to be implied by dist. > > --- Noel Well, I admit that I pass more time on pom.xml files than build.xml files lately, but maybe you want to add a "clean" too. If I understand it correctly "dist" depends only on "clean-dist" that is different from full "clean". The full clean will call clean for each module, instead the clean-dist will clean only the main folder and not the modules. The modules only invoke "conditional-clean" that is not triggered in this case. If you prefer to clean the build.xml instead of changing your build server I have no problem with this. Thank you, Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JAMES Server Nightly Build Report
> What target is/are invoked by the build server? ant dist, since clean is supposed to be implied by dist. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (MAILET-1) Fix commit messages to go to mailet-api@
[ https://issues.apache.org/jira/browse/MAILET-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noel J. Bergman resolved MAILET-1. -- Resolution: Fixed Should be fixed. > Fix commit messages to go to mailet-api@ > > > Key: MAILET-1 > URL: https://issues.apache.org/jira/browse/MAILET-1 > Project: Mailet API > Issue Type: Task > Environment: SVN >Reporter: Danny Angus > Assigned To: Noel J. Bergman > > commits to james/mailet/ currently go to server-dev@ -- 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]
[jira] Assigned: (MAILET-1) Fix commit messages to go to mailet-api@
[ https://issues.apache.org/jira/browse/MAILET-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noel J. Bergman reassigned MAILET-1: Assignee: Noel J. Bergman > Fix commit messages to go to mailet-api@ > > > Key: MAILET-1 > URL: https://issues.apache.org/jira/browse/MAILET-1 > Project: Mailet API > Issue Type: Task > Environment: SVN >Reporter: Danny Angus > Assigned To: Noel J. Bergman > > commits to james/mailet/ currently go to server-dev@ -- 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]
[EMAIL PROTECTED]: Project james-server (in module james-server) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project james-server has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - james-server : James Server Full details are available at: http://vmgump.apache.org/gump/public/james-server/james-server/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [james-server-core-library-03052007.jar] identifier set to project name -DEBUG- Dependency on javamail exists, no need to add for property gump.resource.javamail. -DEBUG- Dependency on magic exists, no need to add for property magic.home. -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/james-server/james-server/gump_work/build_james-server_james-server.html Work Name: build_james-server_james-server (Type: Build) Work ended in a state of : Failed Elapsed: 15 secs Command Line: /opt/jdk1.5/bin/java -Djava.awt.headless=true org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dgump.resource.dnsjava=/usr/local/gump/public/workspace/james-server/stage/dnsjava/jars/dnsjava-2.0.3.jar -Dgump.resource.javamail=/usr/local/gump/packages/javamail-1.4/mail.jar -Dgump.resource.jce=/usr/local/gump/packages/jce/jce-jdk13-116.jar -Dmagic.home=/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/03052007 -Dgump.resource.geronimo-spec-jms=/usr/local/gump/packages/jms1.1/lib/jms.jar -Dgump.resource.cornerstone-scheduler-api=/usr/local/gump/public/workspace/excalibur/cornerstone/scheduler/api/target/excalibur-cornerstone-scheduler-api-03052007.jar -Dgump.resource.commons-logging=/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-03052007.jar -Dgump.resource.excalibur-pool-impl=/usr/local/gump/public/workspace/excalibur/components/pool/impl/target/excalibur-pool-impl-03052007.jar -Dgump.resource.cornerstone-threads-api=/usr/local/gump/public/workspace/excalibur/cornerstone/threads/api/target/excalibur-cornerstone-threads-api-03052007.jar -Dgump.resource.avalon-framework-api=/usr/local/gump/public/workspace/excalibur/framework/api/target/excalibur-framework-api-03052007.jar -Dgump.resource.avalon-logkit=/usr/local/gump/public/workspace/excalibur/containerkit/logkit/target/excalibur-logkit-03052007.jar -Dgump.resource.cornerstone-connection-impl=/usr/local/gump/public/workspace/excalibur/cornerstone/connection/impl/target/excalibur-cornerstone-connection-impl-03052007.jar -Dversion=03052007 -Dgump.resource.cornerstone-datasources-api=/usr/local/gump/public/workspace/excalibur/cornerstone/datasources/api/target/excalibur-cornerstone-datasources-api-03052007.jar -Dgump.resource.cornerstone-store-api=/usr/local/gump/public/workspace/excalibur/cornerstone/store/api/target/excalibur-cornerstone-store-api-03052007.jar -Dbuild.sysclasspath=last -Dgump.resource.log4j=/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-03052007.jar -Dgump.resource.cornerstone-connection-api=/usr/local/gump/public/workspace/excalibur/cornerstone/connection/api/target/excalibur-cornerstone-connection-api-03052007.jar -Dgump.resource.commons-net=/usr/local/gump/public/workspace/jakarta-commons/net/dist/commons-net-03052007.jar -Dgump.resource.commons-pool=/usr/local/gump/public/workspace/jakarta-commons/pool/dist/commons-pool.jar -Dgump.resource.bcmail=/usr/local/gump/packages/bouncycastle-jdk14/bcmail-130.jar -Dgump.signature=03052007 -Dgump.resource.commons-dbcp=/usr/local/gump/public/workspace/jakarta-commons/dbcp/dist/commons-dbcp.jar -Dgump.resource.mailapi=/usr/local/gump/packages/javamail-1.4/mail.jar -Dgump.resource.excalibur-pool-api=/usr/local/gump/public/workspace/excalibur/components/pool/api/target/excalibur-pool-api-03052007.jar -Dgump.resource.excalibur-thread-api=/usr/local/gump/public/workspace/excalibur/components/thread/api/target/excalibur-thread-api-03052007.jar -Dgump.resource.bcprov=/usr/local/gump/packages/bouncycastle-jdk14/bcprov-130.jar -Dgump.resource.cornerstone-sockets-api=/usr/local/gump/public/workspace/excalibur/cornerstone/sockets/api/target/excalibur-cornerstone-sockets-api-03052007.jar -Dgump.resource.cornerstone-threads-impl=/usr/local/gump/public/workspace/excalibur/cornerstone/threads/impl/target/excalibur-cornerstone-threads-impl-03052007.jar -Dgump.resource.servletapi=/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar -Dgump.resource.avalon-meta-tools=/usr/local/gump/public/workspace/avalon-trunk/r
[EMAIL PROTECTED]: Project james-server (in module james-server) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project james-server has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - james-server : James Server Full details are available at: http://vmgump.apache.org/gump/public/james-server/james-server/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [james-server-core-library-03052007.jar] identifier set to project name -DEBUG- Dependency on javamail exists, no need to add for property gump.resource.javamail. -DEBUG- Dependency on magic exists, no need to add for property magic.home. -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/james-server/james-server/gump_work/build_james-server_james-server.html Work Name: build_james-server_james-server (Type: Build) Work ended in a state of : Failed Elapsed: 15 secs Command Line: /opt/jdk1.5/bin/java -Djava.awt.headless=true org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dgump.resource.dnsjava=/usr/local/gump/public/workspace/james-server/stage/dnsjava/jars/dnsjava-2.0.3.jar -Dgump.resource.javamail=/usr/local/gump/packages/javamail-1.4/mail.jar -Dgump.resource.jce=/usr/local/gump/packages/jce/jce-jdk13-116.jar -Dmagic.home=/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/03052007 -Dgump.resource.geronimo-spec-jms=/usr/local/gump/packages/jms1.1/lib/jms.jar -Dgump.resource.cornerstone-scheduler-api=/usr/local/gump/public/workspace/excalibur/cornerstone/scheduler/api/target/excalibur-cornerstone-scheduler-api-03052007.jar -Dgump.resource.commons-logging=/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-03052007.jar -Dgump.resource.excalibur-pool-impl=/usr/local/gump/public/workspace/excalibur/components/pool/impl/target/excalibur-pool-impl-03052007.jar -Dgump.resource.cornerstone-threads-api=/usr/local/gump/public/workspace/excalibur/cornerstone/threads/api/target/excalibur-cornerstone-threads-api-03052007.jar -Dgump.resource.avalon-framework-api=/usr/local/gump/public/workspace/excalibur/framework/api/target/excalibur-framework-api-03052007.jar -Dgump.resource.avalon-logkit=/usr/local/gump/public/workspace/excalibur/containerkit/logkit/target/excalibur-logkit-03052007.jar -Dgump.resource.cornerstone-connection-impl=/usr/local/gump/public/workspace/excalibur/cornerstone/connection/impl/target/excalibur-cornerstone-connection-impl-03052007.jar -Dversion=03052007 -Dgump.resource.cornerstone-datasources-api=/usr/local/gump/public/workspace/excalibur/cornerstone/datasources/api/target/excalibur-cornerstone-datasources-api-03052007.jar -Dgump.resource.cornerstone-store-api=/usr/local/gump/public/workspace/excalibur/cornerstone/store/api/target/excalibur-cornerstone-store-api-03052007.jar -Dbuild.sysclasspath=last -Dgump.resource.log4j=/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-03052007.jar -Dgump.resource.cornerstone-connection-api=/usr/local/gump/public/workspace/excalibur/cornerstone/connection/api/target/excalibur-cornerstone-connection-api-03052007.jar -Dgump.resource.commons-net=/usr/local/gump/public/workspace/jakarta-commons/net/dist/commons-net-03052007.jar -Dgump.resource.commons-pool=/usr/local/gump/public/workspace/jakarta-commons/pool/dist/commons-pool.jar -Dgump.resource.bcmail=/usr/local/gump/packages/bouncycastle-jdk14/bcmail-130.jar -Dgump.signature=03052007 -Dgump.resource.commons-dbcp=/usr/local/gump/public/workspace/jakarta-commons/dbcp/dist/commons-dbcp.jar -Dgump.resource.mailapi=/usr/local/gump/packages/javamail-1.4/mail.jar -Dgump.resource.excalibur-pool-api=/usr/local/gump/public/workspace/excalibur/components/pool/api/target/excalibur-pool-api-03052007.jar -Dgump.resource.excalibur-thread-api=/usr/local/gump/public/workspace/excalibur/components/thread/api/target/excalibur-thread-api-03052007.jar -Dgump.resource.bcprov=/usr/local/gump/packages/bouncycastle-jdk14/bcprov-130.jar -Dgump.resource.cornerstone-sockets-api=/usr/local/gump/public/workspace/excalibur/cornerstone/sockets/api/target/excalibur-cornerstone-sockets-api-03052007.jar -Dgump.resource.cornerstone-threads-impl=/usr/local/gump/public/workspace/excalibur/cornerstone/threads/impl/target/excalibur-cornerstone-threads-impl-03052007.jar -Dgump.resource.servletapi=/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar -Dgump.resource.avalon-meta-tools=/usr/local/gump/public/workspace/avalon-trunk/r
Re: JAMES Server Nightly Build Report
Noel J. Bergman ha scritto: >> Yeah there's something wrong, it should have failed because >> org.apache.mailet.Mail cannot be found. > > At a quick glance, it seems that the build script isn't cleaning the staging > area. And artifacts that are dependencies are conflated with artifacts that > we generate during the build, so simply doing `rm stage/org.apache.james/*` > isn't the answer, although removing stage/o.a.j/james-server* might be a > quick fix. > > --- Noel mm.. weird, because I did this: 1) full build before the update. .worked. 2) update (the update removed the mailet and mailet-api sources) 3) ant clean dist And *I* *saw* the error. What target is/are invoked by the build server? Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (MAILET-3) Create a pom.xml descriptor to build website and deploy artifact to the maven repository
[ https://issues.apache.org/jira/browse/MAILET-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefano Bagnara reassigned MAILET-3: Assignee: Stefano Bagnara > Create a pom.xml descriptor to build website and deploy artifact to the maven > repository > > > Key: MAILET-3 > URL: https://issues.apache.org/jira/browse/MAILET-3 > Project: Mailet API > Issue Type: Task >Reporter: Stefano Bagnara > Assigned To: Stefano Bagnara > -- 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]
[jira] Created: (MAILET-4) Create a minimal website for mailet product/subproject
Create a minimal website for mailet product/subproject -- Key: MAILET-4 URL: https://issues.apache.org/jira/browse/MAILET-4 Project: Mailet API Issue Type: Wish Reporter: Stefano Bagnara Maybe starting from here: http://wiki.apache.org/james/MailetAPI -- 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]
[jira] Created: (MAILET-3) Create a pom.xml descriptor to build website and deploy artifact to the maven repository
Create a pom.xml descriptor to build website and deploy artifact to the maven repository Key: MAILET-3 URL: https://issues.apache.org/jira/browse/MAILET-3 Project: Mailet API Issue Type: Task Reporter: Stefano Bagnara -- 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]
[jira] Created: (MAILET-2) Mailet move breaks Gump
Mailet move breaks Gump --- Key: MAILET-2 URL: https://issues.apache.org/jira/browse/MAILET-2 Project: Mailet API Issue Type: Task Reporter: Danny Angus Set up mailet api in gump. -- 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]
[jira] Created: (MAILET-1) Fix commit messages to go to mailet-api@
Fix commit messages to go to mailet-api@ Key: MAILET-1 URL: https://issues.apache.org/jira/browse/MAILET-1 Project: Mailet API Issue Type: Task Environment: SVN Reporter: Danny Angus commits to james/mailet/ currently go to server-dev@ -- 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]
Re: i am not getting subject content in utf-8 format
On 5/4/07, ketanbparekh <[EMAIL PROTECTED]> wrote: I am trying to filter mails by passing persian words in subject. But persian words appear as ? marks in subject and jsieve is not able to filter it. This is a complex area, and it really depends where the corruption is occuring. You need to ensure that the software which creates the message, your sieve scripts, and the software you use to view it all are using UTF-8. Then if there is still a problem we need to make sure that the charset is properly recorded in the headers, and that the header is escaped correctly using base64 or Uuencode. d. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JAMES Server Nightly Build Report
> Yeah there's something wrong, it should have failed because > org.apache.mailet.Mail cannot be found. At a quick glance, it seems that the build script isn't cleaning the staging area. And artifacts that are dependencies are conflated with artifacts that we generate during the build, so simply doing `rm stage/org.apache.james/*` isn't the answer, although removing stage/o.a.j/james-server* might be a quick fix. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
i am not getting subject content in utf-8 format
Hi all, I am trying to filter mails by passing persian words in subject. But persian words appear as ? marks in subject and jsieve is not able to filter it. Can anybody pls provide me the solution, I want to filter persian or other language words(UTF-8 format) that appear in subject. Thanks in advance, Ketan.B.Parekh -- View this message in context: http://www.nabble.com/i-am-not-getting-subject-content-in-utf-8-format-tf3691572.html#a10321022 Sent from the James - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAMES Server Nightly Build Report
Check-in complete I *think* it works now. On 5/4/07, Danny Angus <[EMAIL PROTECTED]> wrote: p.s. I'm working on it, all I have left to do is get the new jar to copy into the dist. otherwise it all compiles and the tests all pass d. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r535161 - in /james/server/trunk: build-tools/base-build.xml include.properties mailet-api/ mailet/ phoenix-deployment/build.xml stage/org.apache.james/jars/mailet-2.3-SNAPSHOT.jar
Author: danny
Date: Fri May 4 03:50:31 2007
New Revision: 535161
URL: http://svn.apache.org/viewvc?view=rev&rev=535161
Log:
fixing the build
Added:
james/server/trunk/stage/org.apache.james/jars/mailet-2.3-SNAPSHOT.jar
(with props)
Removed:
james/server/trunk/mailet/
james/server/trunk/mailet-api/
Modified:
james/server/trunk/build-tools/base-build.xml
james/server/trunk/include.properties
james/server/trunk/phoenix-deployment/build.xml
Modified: james/server/trunk/build-tools/base-build.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/build-tools/base-build.xml?view=diff&rev=535161&r1=535160&r2=535161
==
--- james/server/trunk/build-tools/base-build.xml (original)
+++ james/server/trunk/build-tools/base-build.xml Fri May 4 03:50:31 2007
@@ -182,6 +182,7 @@
+
Modified: james/server/trunk/include.properties
URL:
http://svn.apache.org/viewvc/james/server/trunk/include.properties?view=diff&rev=535161&r1=535160&r2=535161
==
--- james/server/trunk/include.properties (original)
+++ james/server/trunk/include.properties Fri May 4 03:50:31 2007
@@ -204,6 +204,11 @@
jarname.commons-digester.jar=commons-digester-1.8.jar
commons-digester.jar=${path.lib.commonsdigester}/${jarname.commons-digester.jar}
+# - mailet-
+jarname.mailet.jar=mailet-2.3-SNAPSHOT.jar
+mailet.jar=${path.lib.james}/${jarname.mailet.jar}
+
+
# - Logging
jarname.avalon-logkit.jar=avalon-logkit-2.1.jar
avalon-logkit.jar=${path.lib.logkit}/${jarname.avalon-logkit.jar}
Modified: james/server/trunk/phoenix-deployment/build.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/phoenix-deployment/build.xml?view=diff&rev=535161&r1=535160&r2=535161
==
--- james/server/trunk/phoenix-deployment/build.xml (original)
+++ james/server/trunk/phoenix-deployment/build.xml Fri May 4 03:50:31 2007
@@ -98,6 +98,7 @@
+
@@ -367,28 +368,7 @@
-
-
+
-
-
-
-
-
-
-
-
+
+
@@ -516,8 +484,6 @@
-
-
@@ -558,6 +524,7 @@
+
@@ -604,13 +571,6 @@
-
-
-
-
Added: james/server/trunk/stage/org.apache.james/jars/mailet-2.3-SNAPSHOT.jar
URL:
http://svn.apache.org/viewvc/james/server/trunk/stage/org.apache.james/jars/mailet-2.3-SNAPSHOT.jar?view=auto&rev=535161
==
Binary file - no diff available.
Propchange:
james/server/trunk/stage/org.apache.james/jars/mailet-2.3-SNAPSHOT.jar
--
svn:mime-type = application/octet-stream
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAMES Server Nightly Build Report
p.s. I'm working on it, all I have left to do is get the new jar to copy into the dist. otherwise it all compiles and the tests all pass d. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAMES Server Nightly Build Report
On 5/4/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: Isn't there something wrong? The Nightly build worked even without the mailet and mailet-api modules !? Noel, maybe the build server does not correctly cleanup everything? Here it "correctly" fails. Yeah there's something wrong, it should have failed because org.apache.mailet.Mail cannot be found. d. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [mime4j] null charset error
Hi Stefano
Sorry about that.. I made the mistake of switching to windows live (beta)
and it screwed thing up..
hope this is clearer
GX
From: Stefano Bagnara <[EMAIL PROTECTED]>
Reply-To: "James Developers List"
To: James Developers List
Subject: Re: [mime4j] null charset error
Date: Fri, 04 May 2007 11:19:36 +0200
This message come through totally unformatted.
I formatted it and opened a JIRA issue [1] so we can track it.
Thank you,
Stefano
[1] http://issues.apache.org/jira/browse/MIME4J-12
GX GLIX ha scritto:
>
Hi all
I sincerely apologise for the delay, I have had other priorities and had to
put this aside till now, after futher debugging I have come across the cause
of the java.io.IOException: Bad file descriptor error.
In the file /org/mime4j/message/Header.java the following code is found
public void writeTo(OutputStream out) throws IOException {
String charString = ((ContentTypeField)
getField(Field.CONTENT_TYPE)).getCharset();
BufferedWriter writer = new BufferedWriter(new
OutputStreamWriter(out, CharsetUtil.getCharset(charString)),8192);
writer.write(toString()+ "\r\n");
writer.flush();
writer.close();
}
as you can see the output stream is closed here. This is cause of the
IOException as the stream is used later again for writing.
I tried commenting the writer.close(); call and it worked fine, however I
dont know what the implications of this may be.
The case I am facing is a multipart message which calls the writeTo method
below
public void writeTo(OutputStream out) throws IOException {
getHeader().writeTo(out);
Body body = getBody();
if (body instanceof Multipart) {
Multipart mp = (Multipart) body;
mp.writeTo(out);
} else {
body.writeTo(out);
}
}
when getHeader().writeTo(out); is called the stream is closed and when
mp.writeTo(out); is called the exception is throw as the stream is closed.
Regards
GX
>From: Norman Maurer <[EMAIL PROTECTED]>> >Reply-To: "Jam
es Developers List" > >To: James Developers
List > >Subject: Re: [mime4j] null charset
error> >Date: Tue, 24 Apr 2007 15:36:34 +0200> >> >Hi GX,> >> >what JDK and
OS you using? I found some intressting stuff:> >>
>http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322678>
>http://256.com/gray/docs/misc/java_bad_file_descriptor_close_bug.shtml>
>> >bye> >Norman> >> >> >GX GLIX schrieb:> > > Hi All> > >> > > I am
getting a "Null charset name" error during parsing, it seems that> > >
getCharset(String charsetName) is passed an empty string... I tried> > >
the following hack to fix it:> > >> > > ..> > >public static
java.nio.charset.Charset getCharset(String> > > charsetName) {> > >
if(charsetName == null)> > >charsetName = "ISO8859-1";> > >
java.nio.charset.Charset c => > >
java.nio.charset.Charset.forName(charsetName);> > > > > >> > >
now the result is :> > >> > > java.i
o.IOException: Bad file descriptor> > > at
java.io.FileOutputStream.writeBytes(Native Method)> > > at
java.io.FileOutputStream.write(FileOutputStream.java:260)> > > at> > >
sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)> > >
at> > > >
>sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)>
> >> > > at> > >
sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)> > >
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)> > > at
java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)> > > at
java.io.BufferedWriter.flush(BufferedWriter.java:230)> > > at
org.mime4j.message.Header.writeTo(Header.java:152)> > > at
org.mime4j.message.BodyPart.writeTo(BodyPart.java:39)> > > at
org.mime4j.message.Multipart.writeTo(Multipart.java:178)> > > at
org.mime4j.message.Message.writeTo(Message.java:91)> > > any ideas anyone?>
> >> > > ___
__> > > FREE pop-up blocking with the new MSN Toolbar - get
it now!> > > http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/>
> >> > >> > >
-> > >
To unsubscribe, e-mail: [EMAIL PROTECTED]> > > For
additional commands, e-mail: [EMAIL PROTECTED]> > >> > >> >
> !DSPAM:1,462c94fb324321289648189!> > >> > >> >> >>
>->
>To unsubscribe, e-mail: [EMAIL PROTECTED]> >For
additional commands, e-mail: [EMAIL PROTECTED]> >> >
_> Express
yourself instantly with MSN Messenger! Download today it's FREE! >
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/> > >
-> To
unsubscribe, e-mail: [EMAIL PROTECTED]
ache.org> For additional commands, e-mail:
[EMAIL PROTECTED]>
-
Re: [mime4j] Licensing & Co.
Niklas Therning ha scritto: > Stefano Bagnara wrote: >> Please, Niklas, take a look at the test artifacts I published here: >> http://people.apache.org/~bago/mime4j/ >> >> Thank you, >> Stefano > > The files look great! mvn package worked as expected too. Great work > Stefano! Thanks to you for reviewing :-) I'm going to delay the release vote because of 1) https://issues.apache.org/jira/browse/MIME4J-12 2) I want to refactor the maven build to use the remote-resources-plugin (http://maven.apache.org/plugins/maven-remote-resources-plugin/) to generate the appropriate LICENSE and NOTICE files. The current hack including the root files as resources creates some problem to other plugins. Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [mime4j] null charset error
This message come through totally unformatted.
I formatted it and opened a JIRA issue [1] so we can track it.
Thank you,
Stefano
[1] http://issues.apache.org/jira/browse/MIME4J-12
GX GLIX ha scritto:
> Hi allI sincerely apologise for the delay, I have had other priorities and
> had to put this aside till now, after futher debugging I have come across the
> cause of the java.io.IOException: Bad file descriptor error.In the file
> /org/mime4j/message/Header.java the following code is foundpublic void
> writeTo(OutputStream out) throws IOException {String charString =
> ((ContentTypeField) getField(Field.CONTENT_TYPE)).getCharset();
> BufferedWriter writer = new BufferedWriter(new OutputStreamWriter(out,
> CharsetUtil.getCharset(charString)),8192);writer.write(toString()+
> "\r\n");writer.flush();writer.close();}as you can see the
> output stream is closed here. This is cause of the IOException as the stream
> is used later again for writing.I tried commenting the writer.close(); call
> and it worked fine, however I dont know what the implications of this may
> be.The case I am facing is a multipart message which calls the writeTo method
> below
public void writeTo(OutputStream out) throws IOException {
getHeader().writeTo(out);Body body = getBody();if (body
instanceof Multipart) {Multipart mp = (Multipart) body;
mp.writeTo(out);} else {body.writeTo(out);}
}when getHeader().writeTo(out); is called the stream is closed and when
mp.writeTo(out); is called the exception is throw as the stream is
closed.Regards GX> From: [EMAIL PROTECTED]> To: server-dev@james.apache.org>
Subject: Re: [mime4j] null charset error> Date: Thu, 26 Apr 2007 18:07:11
+0300> > Hi Norman Maurer> > Thanks again your your time and suggestions,> >
Although we are using windows 2003 server the JDK is 1.4, and the submitted >
bug is for jdk 1.6> As am busy with other things for the moment I only be able
to look into this > after the next few days, If I do manage to find anything I
will keep you > posted.> > GX> > >From: Norman Maurer <[EMAIL PROTECTED]>>
>Reply-To: "Jam
es Developers List" > >To: James Developers List
> >Subject: Re: [mime4j] null charset error>
>Date: Tue, 24 Apr 2007 15:36:34 +0200> >> >Hi GX,> >> >what JDK and OS you
using? I found some intressting stuff:> >>
>http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322678>
>http://256.com/gray/docs/misc/java_bad_file_descriptor_close_bug.shtml> >>
>bye> >Norman> >> >> >GX GLIX schrieb:> > > Hi All> > >> > > I am getting a
"Null charset name" error during parsing, it seems that> > > getCharset(String
charsetName) is passed an empty string... I tried> > > the following hack to
fix it:> > >> > > ..> > >public static java.nio.charset.Charset
getCharset(String> > > charsetName) {> > >if(charsetName == null)> > >
charsetName = "ISO8859-1";> > >java.nio.charset.Charset c =>
> > java.nio.charset.Charset.forName(charsetName);> > > > > >> > >
now the result is :> > >> > > java.i
o.IOException: Bad file descriptor> > > at
java.io.FileOutputStream.writeBytes(Native Method)> > > at
java.io.FileOutputStream.write(FileOutputStream.java:260)> > > at> > >
sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)> > >
at> > > >
>sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)> >
>> > > at> > >
sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)> > >
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)> > > at
java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)> > > at
java.io.BufferedWriter.flush(BufferedWriter.java:230)> > > at
org.mime4j.message.Header.writeTo(Header.java:152)> > > at
org.mime4j.message.BodyPart.writeTo(BodyPart.java:39)> > > at
org.mime4j.message.Multipart.writeTo(Multipart.java:178)> > > at
org.mime4j.message.Message.writeTo(Message.java:91)> > > any ideas anyone?> >
>> > > ___
__> > > FREE pop-up blocking with the new MSN Toolbar - get it
now!> > > http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/> > >> >
>> > > -> >
> To unsubscribe, e-mail: [EMAIL PROTECTED]> > > For additional commands,
e-mail: [EMAIL PROTECTED]> > >> > >> > > !DSPAM:1,462c94fb324321289648189!> >
>> > >> >> >>
>-> >To
unsubscribe, e-mail: [EMAIL PROTECTED]> >For additional commands, e-mail:
[EMAIL PROTECTED]> >> >
_> Express
yourself instantly with MSN Messenger! Download today it's FREE! >
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/> > >
-
[jira] Created: (MIME4J-12) WriteTo closes the outputstream too early (java.io.IOException: Bad file descriptor error)
WriteTo closes the outputstream too early (java.io.IOException: Bad file
descriptor error)
--
Key: MIME4J-12
URL: https://issues.apache.org/jira/browse/MIME4J-12
Project: Mime4j
Issue Type: Bug
Affects Versions: 0.3
Reporter: Stefano Bagnara
Fix For: 0.3
On server-dev, GX GLIX reported this:
---
Hi all
I sincerely apologise for the delay, I have had other priorities and had to put
this aside till now, after futher debugging I have come across the cause of the
java.io.IOException: Bad file descriptor error.
In the file /org/mime4j/message/Header.java the following code is found
public void writeTo(OutputStream out) throws IOException {
String charString = ((ContentTypeField)
getField(Field.CONTENT_TYPE)).getCharset();
BufferedWriter writer = new BufferedWriter(new OutputStreamWriter(out,
CharsetUtil.getCharset(charString)),8192);
writer.write(toString()+ "\r\n");
writer.flush();
writer.close();
}
as you can see the output stream is closed here.
This is cause of the IOException as the stream is used later again for writing.
I tried commenting the writer.close(); call and it worked fine, however I dont
know what the implications of this may be.
The case I am facing is a multipart message which calls the writeTo method below
public void writeTo(OutputStream out) throws IOException {
getHeader().writeTo(out);
Body body = getBody();
if (body instanceof Multipart) {
Multipart mp = (Multipart) body;
mp.writeTo(out);
} else {
body.writeTo(out);
}
}
when getHeader().writeTo(out); is called the stream is closed and when
mp.writeTo(out); is called the exception is throw as the stream is
closed.Regards
--
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]
Re: JAMES Server Nightly Build Report
Isn't there something wrong? The Nightly build worked even without the mailet and mailet-api modules !? Noel, maybe the build server does not correctly cleanup everything? Here it "correctly" fails. Stefano JAMES Nightly Build System ha scritto: > > Updating From Source Control > > Dmailet-api/src/main/java/org/apache/mailet/MailetContext.java > Dmailet-api/src/main/java/org/apache/mailet/MailetConfig.java > Dmailet-api/src/main/java/org/apache/mailet/Mail.java > Dmailet-api/src/main/java/org/apache/mailet/MailAddress.java > Dmailet-api/src/main/java/org/apache/mailet/MailetException.java > Dmailet-api/src/main/java/org/apache/mailet/Mailet.java > Dmailet/src/main > Updated to revision 535121. > > Do a Clean Build with Unit Tests and Distribution Packages > > [...] > BUILD SUCCESSFUL > Total time: 3 minutes 39 seconds > > Done. Packages Will Be Uploaded To The Nightly Repository. > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mailet sub-project is alive :-)
On 5/3/07, Norman Maurer <[EMAIL PROTECTED]> wrote: Hi Danny, nice to see you found the time :-) Sorry I didn't fix server before the nightly build, I'm doing it now though. d. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [mime4j] null charset error
Hi allI sincerely apologise for the delay, I have had other priorities and had
to put this aside till now, after futher debugging I have come across the cause
of the java.io.IOException: Bad file descriptor error.In the file
/org/mime4j/message/Header.java the following code is foundpublic void
writeTo(OutputStream out) throws IOException {String charString =
((ContentTypeField) getField(Field.CONTENT_TYPE)).getCharset();
BufferedWriter writer = new BufferedWriter(new OutputStreamWriter(out,
CharsetUtil.getCharset(charString)),8192);writer.write(toString()+
"\r\n");writer.flush();writer.close();}as you can see the
output stream is closed here. This is cause of the IOException as the stream is
used later again for writing.I tried commenting the writer.close(); call and it
worked fine, however I dont know what the implications of this may be.The case
I am facing is a multipart message which calls the writeTo method below
public void writeTo(OutputStream out) throws IOException {
getHeader().writeTo(out);Body body = getBody();if (body
instanceof Multipart) {Multipart mp = (Multipart) body;
mp.writeTo(out);} else {body.writeTo(out);}
}when getHeader().writeTo(out); is called the stream is closed and when
mp.writeTo(out); is called the exception is throw as the stream is
closed.Regards GX> From: [EMAIL PROTECTED]> To: server-dev@james.apache.org>
Subject: Re: [mime4j] null charset error> Date: Thu, 26 Apr 2007 18:07:11
+0300> > Hi Norman Maurer> > Thanks again your your time and suggestions,> >
Although we are using windows 2003 server the JDK is 1.4, and the submitted >
bug is for jdk 1.6> As am busy with other things for the moment I only be able
to look into this > after the next few days, If I do manage to find anything I
will keep you > posted.> > GX> > >From: Norman Maurer <[EMAIL PROTECTED]>>
>Reply-To: "James Developers List" > >To: James
Developers List > >Subject: Re: [mime4j] null
charset error> >Date: Tue, 24 Apr 2007 15:36:34 +0200> >> >Hi GX,> >> >what JDK
and OS you using? I found some intressting stuff:> >>
>http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322678>
>http://256.com/gray/docs/misc/java_bad_file_descriptor_close_bug.shtml> >>
>bye> >Norman> >> >> >GX GLIX schrieb:> > > Hi All> > >> > > I am getting a
"Null charset name" error during parsing, it seems that> > > getCharset(String
charsetName) is passed an empty string... I tried> > > the following hack to
fix it:> > >> > > ..> > >public static java.nio.charset.Charset
getCharset(String> > > charsetName) {> > >if(charsetName == null)> > >
charsetName = "ISO8859-1";> > >java.nio.charset.Charset c =>
> > java.nio.charset.Charset.forName(charsetName);> > > > > >> > >
now the result is :> > >> > > java.io.IOException: Bad file descriptor> > >
at java.io.FileOutputStream.writeBytes(Native Method)> > > at
java.io.FileOutputStream.write(FileOutputStream.java:260)> > > at> > >
sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)> > >
at> > > >
>sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)> >
>> > > at> > >
sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)> > >
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)> > > at
java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)> > > at
java.io.BufferedWriter.flush(BufferedWriter.java:230)> > > at
org.mime4j.message.Header.writeTo(Header.java:152)> > > at
org.mime4j.message.BodyPart.writeTo(BodyPart.java:39)> > > at
org.mime4j.message.Multipart.writeTo(Multipart.java:178)> > > at
org.mime4j.message.Message.writeTo(Message.java:91)> > > any ideas anyone?> >
>> > > _> > >
FREE pop-up blocking with the new MSN Toolbar - get it now!> > >
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/> > >> > >> > >
-> > > To
unsubscribe, e-mail: [EMAIL PROTECTED]> > > For additional commands, e-mail:
[EMAIL PROTECTED]> > >> > >> > > !DSPAM:1,462c94fb324321289648189!> > >> > >>
>> >> >->
>To unsubscribe, e-mail: [EMAIL PROTECTED]> >For additional commands, e-mail:
[EMAIL PROTECTED]> >> >
_> Express
yourself instantly with MSN Messenger! Download today it's FREE! >
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/> > >
-> To
unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: [EMAIL
PROTECTED]>
_
Connect to t
JAMES Server Nightly Build Report
Updating From Source Control Dmailet-api/src/main/java/org/apache/mailet/MailetContext.java Dmailet-api/src/main/java/org/apache/mailet/MailetConfig.java Dmailet-api/src/main/java/org/apache/mailet/Mail.java Dmailet-api/src/main/java/org/apache/mailet/MailAddress.java Dmailet-api/src/main/java/org/apache/mailet/MailetException.java Dmailet-api/src/main/java/org/apache/mailet/Mailet.java Dmailet/src/main Updated to revision 535121. Do a Clean Build with Unit Tests and Distribution Packages Buildfile: build.xml clean-dist: [delete] Deleting directory /home/noel/ASF/james/server/trunk/dist [mkdir] Created dir: /home/noel/ASF/james/server/trunk/dist dist: [echo] Building modules, performing standard deployments and creating standard distributions check-environment: [echo] Environment looks okay conditional-clean: master-module-template.set-classpath: set-classpath: build: [echo] Building mailet-api [echo] Compiling src/main/java dist: check-environment: [echo] Environment looks okay conditional-clean: master-module-template.set-classpath: set-classpath: build: [echo] Building mailet-library [echo] Compiling src/main/java [mkdir] Created dir: /home/noel/ASF/james/server/trunk/mailet/src/main/java [mkdir] Created dir: /home/noel/ASF/james/server/trunk/mailet/src/main/resources dist: check-environment: [echo] Environment looks okay conditional-clean: master-module-template.set-classpath: set-classpath: build: [echo] Building core-library [echo] Compiling target/src dist: check-environment: [echo] Environment looks okay conditional-clean: master-module-template.set-classpath: set-classpath: build: [echo] Building fetchmail-function [echo] Compiling src/main/java dist: check-environment: [echo] Environment looks okay conditional-clean: master-module-template.set-classpath: set-classpath: build: [echo] Building imapserver-function [echo] Compiling src/main/java dist: check-environment: [echo] Environment looks okay conditional-clean: master-module-template.set-classpath: set-classpath: build: [echo] Building nntpserver-function [echo] Compiling src/main/java dist: check-environment: [echo] Environment looks okay conditional-clean: master-module-template.set-classpath: set-classpath: build: [echo] Building pop3server-function [echo] Compiling src/main/java dist: check-environment: [echo] Environment looks okay conditional-clean: master-module-template.set-classpath: set-classpath: build: [echo] Building remotemanager-function [echo] Compiling src/main/java dist: check-environment: [echo] Environment looks okay conditional-clean: master-module-template.set-classpath: set-classpath: build: [echo] Building smtpserver-function [echo] Compiling src/main/java dist: check-environment: [echo] Environment looks okay conditional-clean: master-module-template.set-classpath: set-classpath: build: [echo] Building spoolmanager-function [echo] Compiling src/main/java dist: clean: [echo] deleting working directories ready for a clean build [delete] Deleting directory /home/noel/ASF/james/server/trunk/phoenix-deployment/dist/james-server-next-major [delete] Deleting directory /home/noel/ASF/james/server/trunk/phoenix-deployment/target setup-dependencies: javamail-check: activation-check: check-dependencies: prepare-common: [echo] Preparing code [mkdir] Created dir: /home/noel/ASF/james/server/trunk/phoenix-deployment/dist/james-server-next-major [copy] Copying 4 files to /home/noel/ASF/james/server/trunk/phoenix-deployment/dist/james-server-next-major prepare-phoenix: [echo] Phoenix distribution present - adjusting linefeeds and permissions, copying files [copy] Copying 70 files to /home/noel/ASF/james/server/trunk/phoenix-deployment/dist/james-server-next-major [copy] Copying 6 files to /home/noel/ASF/james/server/trunk/phoenix-deployment/dist/james-server-next-major/lib [copy] Copying 1 file to /home/noel/ASF/james/server/trunk/phoenix-deployment/dist/james-server-next-major/bin prepare-mxinfo: [mkdir] Created dir: /home/noel/ASF/james/server/trunk/phoenix-deployment/target/classes [generatemeta] Writing Info descriptors as legacy xml. prepare-metainf: [copy] Copying 1 file to /home/noel/ASF/james/server/trunk/phoenix-deployment/target/meta-inf prepare: compile-main: [echo] Compiling James Java sources [javac] Compiling 1 source file to /home/noel/ASF/james/server/trunk/phoenix-deployment/target/classes [copy] Copyi
