On 01/08/11 18:52, Norman Maurer wrote:
Hi Eugen,
comments inside..
2011/8/1 Ioan Eugen Stan:
Hello,
I'm having some issues putting things together when it comes to
Message implementation. I will explain things right away.
The current code [1], [2], and [3] is based on JPA implementation and
Hi Eugen,
comments inside..
2011/8/1 Ioan Eugen Stan :
> Hello,
>
> I'm having some issues putting things together when it comes to
> Message implementation. I will explain things right away.
> The current code [1], [2], and [3] is based on JPA implementation and
> it copies the message content i
Hello,
I'm having some issues putting things together when it comes to
Message implementation. I will explain things right away.
The current code [1], [2], and [3] is based on JPA implementation and
it copies the message content into byte arrays.
This does not seem to scale too well.
There is als
2011/8/1 Robert Burrell Donkin :
> On Mon, Aug 1, 2011 at 10:18 AM, Norman Maurer wrote:
>> Am 01.08.2011 10:28, schrieb Eric Charles:
>>>
>>> o discuss the way we deploy web sites:
>>>
>>> 1. Via svn (commit in www project, and update on server).
>>> 2. Via svn (commit in www project, and automat
On Mon, Aug 1, 2011 at 10:18 AM, Norman Maurer wrote:
> Am 01.08.2011 10:28, schrieb Eric Charles:
>>
>> o discuss the way we deploy web sites:
>>
>> 1. Via svn (commit in www project, and update on server).
>> 2. Via svn (commit in www project, and automatically visible via
>> svnpubsub).
>> 3. V
Am 01.08.2011 10:28, schrieb Eric Charles:
o discuss the way we deploy web sites:
1. Via svn (commit in www project, and update on server).
2. Via svn (commit in www project, and automatically visible via
svnpubsub).
3. Via scp (with file permissions issues...)
4. Via mvn site-deploy
I unders
2011/8/1 Eric Charles :
> Hi,
>
> We need to discuss the way we deploy web sites:
>
> 1. Via svn (commit in www project, and update on server).
> 2. Via svn (commit in www project, and automatically visible via svnpubsub).
> 3. Via scp (with file permissions issues...)
> 4. Via mvn site-deploy
>
>
Hi,
We need to discuss the way we deploy web sites:
1. Via svn (commit in www project, and update on server).
2. Via svn (commit in www project, and automatically visible via svnpubsub).
3. Via scp (with file permissions issues...)
4. Via mvn site-deploy
I understand there is a consensus for op
On 30/07/11 13:24, Stefano Bagnara wrote:
2011/7/30 Eric Charles:
On 30/07/11 00:42, Stefano Bagnara wrote:
I guess it's an year or more I don't deploy james websites and I found
I don't know the updated way to do that.
I see the svn folder james/sites/trunk/www is outdated so I guess we
don'
On 30/07/11 21:27, Norman Maurer wrote:
Thanks :)
+1
Norman
2011/7/30 Stefano Bagnara:
2011/7/26 Eric Charles:
Can someone update the sample page. I could do it, but it will be much
faster and safer from mime4j specialists.
https://svn.apache.org/repos/asf/james/mime4j/trunk/src/site/ap
10 matches
Mail list logo