----- Original Message -----
From: Pete<[EMAIL PROTECTED]>
> On Sun, 13 Aug 2000, Harmeet Bedi wrote:
> > Is Avalon2.1 compatibity an aim ?
> > Would the work I have done, be useful to someone or the James developers
?
>
> Not sure. Avalon has changed *a lot* since 2.1 and will be
> changing even more so for the moment James will be utilising
> old Avalon stuff. I am not sure if it is useful to update
> James to Avalon 2.1 (BTW what changes were needed ???) but
> it could be. If the diffs are small enough post them to this
> list otherwise chuck them on a web page somewhere.
There were a few package changes, and a few interface changes. Painful, but
not dramatic.
Don't remember all the details, here is probably the 90% changes.
Each of these changes involve multiple files.
Package changes
comment out
import org.apache.avalon.utils.*;
and replace with
import org.apache.avalon.interfaces.*;
import org.apache.java.lang.*;
import org.apache.java.util.*;
change references from Constants, to org.apache.james.Constants
For example in SMTPHandler.java change
Constants.SOFTWARE_VERSION to org.apache.james.Constants.SOFTWARE_VERSION
Code changes
The SocketServer.SocketHandler interface has changed. It does not take the
InetAddress parameter. As far as I can tell(very limited testing), it is
safe to not pass this parameter.
the class Interfaces.java from package org.apache.avalon.interface is used
to obtain references to various modules like Logger, Store etc.
I think that is mostly it. If there is more demand, I can do a diff on all
the files, but then if there is a lot of demand then James should move to
Avalon 2.1 comapibilty, :-)
cheers.
Harmeet
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
